Analytical regression testing on a software build

1. A machine-readable storage medium storing instructions for causing data processing apparatus to perform operations comprising:

initiating a plurality of tests on a software build, each test performed using a portion of the software build corresponding to at least one source file;

storing results data relating to the plurality of tests, the results data further identifying source files associated with each of the plurality of tests;

initiating more than two intermittent builds using access to a source repository, the software build comprising one of the intermittent builds, wherein the source repository is configured to store documents that the more than two intermittent builds use as data during the plurality of tests, wherein the intermittent builds are software builds and are initiated in accordance with a schedule:

initiating the plurality of tests on each of the intermittent builds using the documents to produce a set of results data for each intermittent build;

analyzing the sets of results data to identify correlations between the sets of results data as additional result data stored in a results repository in the form of correlation parameters;

filtering the data stored in the results repository in response to a user request; and

sending a notification message of the correlations to user associated with the build in response to analyzing the sets of results data.

2. The article of claim 1 wherein the machine-readable medium further stores instructions for causing data processing apparatus to perform operations comprising configuring each intermittent build in accordance with stored configuration data, the stored configuration data adapted to provide a consistent configuration for different ones of the intermittent builds.

3. The article of claim 1 wherein the instructions comprise instructions written in a scripting language.

4. A computer-implemented method for testing software, the method comprising:

initiating a plurality of tests on a software build, each test performed using a portion of the software build corresponding to at least one source file;

storing results data relating to the plurality of tests, the results data further identifying source files associated with each of the plurality of tests;

initiating more than two intermittent builds using access to a source repository, the software build comprising one of the intermittent builds, wherein the source repository is configured to store documents that the more than two intermittent builds use as data during the plurality of tests, wherein the intermittent builds are software builds and are initiated in accordance with a schedule;

initiating the plurality of tests on each of the intermittent builds using the documents to produce a set of results data for each intermittent build;

analyzing the sets of results data to identify correlations between the sets of results data as additional result data stored in a results repository in the form of correlation parameters;

filtering the data stored in the results repository in response to a user request; and

sending a notification message of the correlations to a user associated with the build in response to analyzing the sets of results data.

5. The method of claim 4 wherein the more than two intermittent builds use source code from the source repository storing a plurality of discrete sources, one of the intermittent builds comprising the build of the software source files.

6. The method of claim 5 wherein each intermittent build includes at least one revision to at least one of the discrete sources and the user associated with the revision comprises a developer of a discrete source that includes the revision.

7. The method of claim 4 further comprising identifying the user associated with the build based on a role associated with the user and with the correlations.

8. The method of claim 4 further comprising identifying the build based on a revision log comprising information relating to the intermittent builds since the prior build.

9. The method of claim 4 wherein initiating the more than two intermittent builds and initiating the plurality of tests on each of the intermittent builds are initiated in response to a trigger from a scheduling module.

10. The method of claim 4 wherein sending the notification message is based on a subscription associated with the user.

11. The method of claim 4 , wherein the plurality of tests includes a performance test.

12. The method of claim 4 , wherein the plurality of tests includes resource monitoring.

13. The method of claim 4 , wherein the plurality of tests includes a quality measurement formed as an n-dimensional space.

14. A testing system including a digital computer, the testing system comprising:

a memory device that is configured as a source repository to store intermittent builds; and

a processor that is configured to initiate a plurality of tests on a software build, each test performed using a portion of the software build corresponding to at least one source file,

wherein the memory device is further configured to store results data relating to the plurality of tests, the results data further identifying source files associated with each of the plurality of tests,

wherein the processor is further configured to initiate more than two of the intermittent builds using access to the source repository, the software build comprising one of the intermittent builds, wherein the source repository is configured to store documents that the more than two intermittent builds use as data during the plurality of tests, wherein the intermittent builds are software builds and are initiated in accordance with a schedule,

wherein the processor is further configured to initiate the plurality of tests on each of the intermittent builds using the documents to produce a set of results data for each intermittent build,

wherein the processor is further configured to analyze the sets of results data to identify correlations between the sets of results data as additional result data stored in a results repository in the form of correlation parameters,

wherein the processor is further configured to filter the data stored in the results repository in response to a user request, and

wherein the processor is further configured to send a notification message of the correlations to user associated with the build in response to analyzing the sets of results data.

15. The testing system of claim 14 , wherein the plurality of tests includes a performance test.

16. The testing system of claim 14 , wherein the plurality of tests includes resource monitoring.

17. The testing system of claim 14 , wherein the plurality of tests includes an application programming interface test.

18. The testing system of claim 14 , wherein the correlations include a correlation between an error type and a day of a week.

19. The testing system of claim 14 , wherein the plurality of tests includes a quality measurement related to a user interface.

20. The testing system of claim 14 , wherein the plurality of tests includes a quality measurement formed as an n-dimensional space.