Requirements based software testing method

• US 6,725,399 B1
• Filed: 07/15/1999
• Issued: 04/20/2004
• Est. Priority Date: 07/15/1999
• Status: Expired due to Term

• Current Assignee: Micro Focus Incorporated (Open Text Corporation)
• Original Assignee: Compuware Corporation (KKR & Co., Inc.)
• Inventors: Bowman, John
• Primary Examiner(s): Beausoleil, Robert
• Assistant Examiner(s): Wilson, Yolanda L.
• Application Number:
  US09/353,872
• Time in Patent Office: 1,741 Days
• Field of Search: 714/38, 717/124
• US Class Current: 714/38.14
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

A method for testing computer software is described. The method is intended for operation on software which may or may not have been previously subjected to unit and integration tests, to determine if it will meet the specific requirements of an end user. The method is applicable to internally developed, contractor developed, or vendor supplied software. The method includes application in six key process areas. The six key process areas are development of a test plan, development of test cases to support the plan, development of an environment to simulate the technical environment in which the program will operate, test execution in which the tests are executed in a technical environment, compiling and analyzing the results and finally reporting the results in a form whereby the end user can determine both the feasibility of the software system for the specific requirements and any areas where additional testing or modifications are necessary.

Claims

1. A requirements based method for determining the proficiency with which a computer program will perform specific functions under specific environmental conditions, the method comprising:

providing computer software containing a program to perform a specific set of predetermined functions and identifying predetermined actual environmental conditions under which those functions are to be performed;

providing a test plan defining tests to be conducted on said program to simulate said actual environmental conditions;

creating test cases to support the test plan;

preparing a test environment that provides a controlled technical environment for application of the test cases, the test environment incorporating a set of transaction test data generated based upon the actual environmental conditions, whereby test results from application of the test cases reflect expected behavior under the actual environmental conditions;

executing said test cases and recording the results;

analyzing the test results using a pass/fail criteria and error identification and evaluation to determine test case defects, application context defect and application defects, if any; and

preparing a management report based upon the analyzed test results to identify a readiness of the program for performance under the actual environmental conditions.

2. The method of claim 1 wherein the test plan includes at least one test selected from the group consisting of Function test, System test, Performance test, Acceptance test, Regression test, Unit and Integration test.

3. The method of claim 2 wherein the Function test demonstrates availability of predetermined functions under the specific conditions.

4. The method of claim 2 wherein the Systems test tests the availability of a testing configuration of functions expected under the actual environmental conditions.

5. The method of claim 2 wherein the Performance test determines runtime performance expected under the actual environmental conditions.

6. The method of claim 2 wherein the Acceptance test determines whether acceptance criteria validating requirements have been met.

7. The method of claim 2 wherein the Regression test tests whether adverse changes are introduced during Maintenance changes and upgrades.

8. The method of claim 1 wherein said program is subjected to Unit and Integration tests prior to executing said test cases and recording the results.

9. The method of claim 1 wherein the test plan includes program requirements to be validated, requirements not to be evaluated, and requirements which can not be validated.