Abstract: This disclosure relates to a method, article of manufacture, and apparatus for automated time-based testing of a distributed system. In some embodiments, this includes setting a backup schedule for a backup of data on a client using a server scheduler on a server, setting a recover schedule using a client scheduler on the client, wherein the client includes a data simulation for generating the data and a repository, wherein the repository includes attributes of the data and a metadata of the backup, starting the data simulation on the client, according to the backup schedule, from the server, triggering a set of backup scripts to perform the backup of the data generated by the data simulation, and according to the recover schedule, triggering a set of recover scripts to perform a recover of the data on the client.

Abstract: An automation framework for a multi-node environment is described. A first host computer executes a parser, a first execution engine, a first communication component, and a first logger. A second host computer executes a second execution engine, a second communication component, and a second logger. The parser parses a test case suite to identify multiple script instructions to test an application. The first execution engine executes the first script instruction to locally execute the first script instruction. The first communication component communicates an execution request to the second communication component to remotely execute the first script instruction. The second communication component instructs the second execution engine to execute the first script instruction. The first and the second logger log a first and a second result of executing the first script instruction on the first and the second host computer. The first logger outputs the first result and/or the second result.

Abstract: Defining a software test is disclosed. A benchmark complexity for a test case including at least one test step having a check condition and a functionality is defined. The test case is represented as a flow graph in which the check condition of each test step of the test case is represented as an edge of the flow graph and the functionality of each test step is represented as a vertex in the flow graph. A test case complexity is determined by determining a number of independent paths in the flow graph. If the test case complexity as determined based on the number of independent paths exceeds the benchmark complexity, the number of test steps in the test case is reduced.