Abstract: A method, apparatus and program product include an Automatic Testing System for creating a test framework for testing operating system components. The Automatic Testing System resides on a server and includes a master driver which assists in creating test cases and scenarios. The Automatic Testing System issues commands to distribute execution to one or more remote client machines in a cluster through, for instance, an external remote shell program. Results of the command are retrieved, as though it was invoked on the machine directly. The logic and parameters needed to run the test scenarios are stored in a database accessible on the web, and test results are compiled and stored in the database to be sent to any designated test customer.

Abstract: Use Case software analysis techniques are developed into a systematic and organized system in which elements of Use Case test scenarios are used and reused and made available from several hierarchical levels. The system is dynamic and a database of test elements are accumulated over time with system use. The invention thus not only provides the automatic, systematic and organized generation of test plans from Use Case specifications, but it also enhances an existing database of test elements over time, with use.

Abstract: A functional testing and evaluation technique is provided employing an abstraction matrix that describes a complex software component to be tested. The abstraction matrix includes at least one test case scenario and mapped expected results therefore. Test cases are derived from the at least one test case scenario and used to test the software component, thereby generating test results. The test results are automatically evaluated using the abstraction matrix. The evaluating includes comparing a test case to the at least one test case scenario of the abstraction matrix and if a match is found, comparing the test result for that test case with the mapped expected result therefore in the abstraction matrix.

Abstract: A functional testing technique is provided employing an abstraction matrix that describes a complex software component to be tested. The abstraction matrix includes state and event information. The technique is an automated process which parses the abstraction matrix to generate test cases and mapped expected results therefore. The test cases are separated based on layers of the software component and data structures are associated with the separated test cases of the layers. The data structures allow the test cases of the various layers to be uncorrelated. The software component executable is employed to generate test case execution threads from the test cases and mapped expected results for a particular layer. These execution threads can then be executed in parallel, thereby testing the software component.

Abstract: A functional testing and evaluation technique is provided employing an abstraction matrix that describes a complex software component to be tested. The abstraction matrix includes at least one test case scenario and mapped expected results therefore. Test cases are derived from the at least one test case scenario and used to test the software component, thereby generating test results. The test results are automatically evaluated using the abstraction matrix. The evaluating includes comparing a test case to the at least one test case scenario of the abstraction matrix and if a match is found, comparing the test result for that test case with the mapped expected result therefore in the abstraction matrix.

Abstract: A functional testing technique is provided employing an abstraction matrix that describes a complex software component to be tested. The abstraction matrix includes state and event information. The technique is an automated process which parses the abstraction matrix to generate test cases and mapped expected results therefore. The test cases are separated based on layers of the software component and data structures are associated with the separated test cases of the layers. The data structures allow the test cases of the various layers to be uncorrelated. The software component executable is employed to generate test case execution threads from the test cases and mapped expected results for a particular layer. These execution threads can then be executed in parallel, thereby testing the software component.