Difference between revisions of "TestingBrainstorm"

Revision as of 23:04, 18 February 2011

Basic Testing Cluster Plan:

Jordan at Rackspace is setting up a cluster of machines of which some section will be allocated to our testing efforts.

We will be using Jenkins to spawn tests against those machines.

The tests will generally look like the following:

• Reset a machine or set of machines to a specific configuration
• On some machines we will be running the unit tests in a couple of ways and coverage tests
• Some machines we will be targeted by the smoketests (and other applicable integration tests)
• Record results

Repository of Stuff

Building up an ad-hoc repository of existing and proposed tests. Please add links to your Jenkins configs (tarballs are fine) and add descriptions of deployment configurations that you expect to be using so that we can make sure they are tested.

• A bunch of Vagrant/Chef-based setups for getting the smoketests to run: https://gist.github.com/786945

Repository of Ideas

Please add any specific or meta thoughts on testing below so that we can compile a general document to work from (rather than spread it out over an email thread).

• It would be nice to run the tests pre-emptively against merge proposals
• It would be nice to set up a page cataloging test results at a finer granularity than the current Jenkins setups.
• Test with Jenkins with packages
• Test with Jenkins with pip and install virtaulenv