One of the new efforts in Jenkins this year is the acceptance test harness for Jenkins.
We will be doing the Jenkins office hours next week to go over this and sync up and coordinate between people in the community that are trying to work on this.
It'll be April 23rd 11am PT (see what this time is in your time zone) on Google Hangout at http://jenkins-ci.org/hangout. If you are intereste in hacking Jenkins or if you are a large user of Jenkins who have acceptance tests, we are looking forward to seeing you there.
For those of you who haven't looked, this test harness allows you to write blackbox tests of Jenkins and its plugins. It was originally used to test LTS releases, but over the time, it acquired a number of features, such as ...:
- Docker support for launching complex fixtures to test Jenkins with.
- Pluggability to launch Jenkins under test (JUT) in many different environments
- Pluggability to provision Jenkins and slaves from EC2 to test large deployments
- Choice of cucumber or JUnit to write test scripts
We are working on porting over existing test cases, but we'd like to work with users to move their acceptance tests on top of this same harness. The idea is to pool those test cases in the community so that we can test Jenkins and its plugins as we develop them. For this to work, we want tests to have lots of metadata (such as what plugins it touches), and for the harness to have sufficient modularity that different people can run the same scenario against different deployments, including existing instance.