Acceptance tests cases for Jenkins and its plug-ins based on selenium and docker.
Go to file
R. Tyler Croy ee01fbd265 Merge pull request #358 from jenkinsci/declarative
Let's try a declarative
2017-09-21 12:01:41 -07:00
docs Introduced a simpler syntax to override local jars 2017-09-02 16:25:47 -07:00
features Bring features directory back temporarily 2017-02-27 08:36:44 +01:00
src Revert "[JENKINS-41196] demonstrate the capability of loading core component jar" 2017-09-19 10:48:52 +02:00
vagrant recording the locations of the box files 2013-02-15 09:20:17 -08:00
veewee adding tools necessary for tests 2013-02-15 09:20:17 -08:00
.gitignore Ignore all *.log files. 2017-01-11 17:13:05 +01:00
Jenkinsfile Ensure we're always using big beefy machines 2017-09-21 11:24:21 -07:00 Distribute docker contianer to run ATH 2016-12-05 10:24:32 +01:00
dockerinject.groovy Clean up and added Comments 2014-04-12 13:48:15 +02:00
ec2.groovy Redoing the way we obtain form-element-path.hpi 2014-05-12 12:11:33 -07:00 Follow redirects in the fetch script 2012-07-30 02:22:31 -07:00 Directly check for jutserver binary rather than target dir before building. 2014-04-21 13:46:08 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2017-08-02 08:35:03 +02:00 Fix argument expansion 2015-02-25 20:55:50 +01:00
single-plugin.groovy Fix UI plugin installation/upload 2016-10-27 15:35:06 +02:00
unsafe.key forgot to set the home correctly 2014-03-18 18:44:34 -07:00 Merge branch 'master' into 2017-02-15 19:10:35 +01:00

Acceptance tests for Jenkins

A project to flesh out some of the manual test cases for Jenkins LTS in an automated fashion.

Following areas are still worked on:

  • Vagrant-based JenkinsController implementations
master stable
Build Status Build Status

Getting Started

Let's start by running tests locally with JENKINS_WAR=path/to/your/jenkins.war mvn test. This runs the entire test suite with the specified Jenkins war and Firefox, so it will take a while.

Set BROWSER=chrome and install in $PATH if desired. (But tests may fail.)

There is a bit of a delay since we bring up Jenkins for every single test, with it's own sandboxed workspace.

Further Reading

Running tests

Writing tests