Abstract: Test software on a test client dynamically locates necessary files by replacing indirect file references in test code with actual file paths. File paths are determined using one or more root paths couple with one or more test parameters being used as a portion of the actual file path. Multiple root paths may be provided in a prioritized list, such that if a file is not found in a first location, additional locations are checked. Test software on a test controller receives a command to perform a test run and queries a data store for test information. A message is assembled using query results and delivered to one or more test clients for execution.

Abstract: The integrated test framework of the present invention includes a test framework runtime that executes test scripts and that also allows a script to identify a variation tool called a “data provider” that is responsible for providing data to the test framework runtime and controlling the iteration of the runtime through the variations. The script also identifies the type of data set from which the data provider should obtain the data from which the variations are derived and the location of the data set. Multiple variation data providers may be used in conjunction with an adapter layer that coordinates the iteration of each variation data provider and creates an aggregated variation over multiple varying parameters of different scope.

Abstract: The present invention is directed towards a test case inheritance behavior that can be controlled via attributes. A base test class from which test objects are derived are useful for reducing test case code and management. For example, base test classes and their derived objects can be used to implement steps that are common between the entire set of classes (e.g., launching a piece of software to be tested and getting it to a certain stage). The principle of inheritance simplifies management of the test software when, for example, the base class is modified, all of the tests which derive from that test case automatically are modified. Accordingly, only one item needs to be modified (instead of every tests) when a change is necessary to modify the way the software launches.