End to end test suite for Jenkins automation server and its plugins.

The scenarios are described in the form of tests controlling Jenkins under test (JUT) through UI / REST APIs. Clean instances are started for individual tests to isolate the tests. The harness provides convenient docker support so integration tests can be written easily.

Follow the contributing guidelines if you want to propose new tests for this project.

The simplest way to start the harness is calling BROWSER=firefox JENKINS_VERSION=2.73 mvn test. The complete test suite takes hours to run due to the number of covered components/use-cases, the cost of Jenkins setup, and selenium interactions. That can be avoided by selecting a subset of tests to be run - smoke tests for instance.

The harness provides a variety of ways to configure the execution including:

• Selecting web browser
• Specifying test(s) to run
• Managing the versions of Jenkins and plugins
• Using a http proxy
• Prelaunching Jenkins
• Selecting how to launch Jenkins
• Obtaining a report of plugins that were exercised
• Running tests in container
• Running tests on Java 11 (WIP)
• Debugging tests in container
• Capture a support bundle
• Selecting tests based on plugins they cover (TODO)

Given how long it takes for the suite to run, test authors are advised to focus on the most popular plugins and use-cases to maximize the value of the test suite. Tests that can or already are written as a part of core/plugin tests should be avoided here as well as tests unlikely to catch future regressions (reproducers for individual bugs, boundary condition testing, etc.). Individual maintainers are expected to update their tests reflecting core/plugin changes as well as ensuring the tests does not produce false positives. Tests identified to violate this guideline might be removed without author's notice for the sake of suite reliability.

• Selenium test in plugin repository
• Docker fixtures
• Page objects
  • Mix-ins
• Guice is our glue
• Writing tests
  • Video tutorial by Kohsuke on how to write tests
  • Writing JUnit test
• Testing slaves
• Hamcrest matchers
• EC2 provider configuration
• Investigation

Areas where acceptance-tests-harness is more suitable then jenkins-test-harness are:

• Installing plugins for cross-plugin integration
• Running tests in a realistic classloader environment
• Verifying UI behaviour in an actual web browser