Hierarchical testing environment

• US 5,421,004 A
• Filed: 09/24/1992
• Issued: 05/30/1995
• Est. Priority Date: 09/24/1992
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Claussen, Christopher S., Cox, James O., Carpenter, Eric R.
• Primary Examiner(s): ATKINSON, CHARLES
• Application Number:
  US07/950,841
• Time in Patent Office: 978 Days
• Field of Search: 371/15.1, 371/16.1, 395/575, 364/578
• US Class Current: 714/25
• CPC Class Codes: G06F 11/2736 using a dedicated service processor for test
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 2201/805 Real-time

Abstract

Disclosed is a method and system for providing a complex testing framework/scaffold. Also included are testing tools that automate and simplify the testing process. The disclosed design handles networking and task concurrency. The testing scaffold is aimed at being a flexible test case driver that can be used to execute functional verification tests on a single host or large networked system level integration tests involving dozens of hosts. The testing scaffold is designed to meet the requirements of large scale testing environments. The ability to execute these environments similarly allows manipulation of smaller scale environments.

Claims

1. A system for providing a hierarchical testing environment, comprising:

a succession of multiple test scenario levels coupled one to another, each multiple test scenario level having at least one scenario;

at least one data file for representing said at least one scenario; and

means for invoking a lower level of said multiple test scenario levels by a higher level of said multiple test scenario levels based upon data contained within said at least one data file.

2. The system of claim 1 wherein said at least one data file comprises configuration information.

3. The system of claim 1 wherein said lower level comprises a plurality of instances.

4. The system of claim 3 wherein said means for invoking a lower level comprises means for invoking an instance in said lower level.

5. The system of claim 3 wherein said means for invoking a lower level comprises means for invoking a plurality of instances in said lower level.

6. The system of claim 5 wherein said means for invoking a plurality of instances comprises means for concurrently invoking a plurality of instances.

7. A multi-computer system for providing a hierarchical testing environment, comprising:

a succession of multiple test scenario levels in each computer, said multiple test scenario levels coupled one to another, with each multiple test scenario level having at least one scenario;

at least one data file for representing said at least one scenario; and

means for invoking a lower level of said multiple test scenario by a higher level of said multiple test scenario based upon data contained within said at least one data file.

8. The system of claim 7 wherein said at least one data file comprises configuration information.

9. The system of claim 7 wherein said lower level comprises a plurality of instances.

10. The system of claim 9 wherein said means for invoking a lower level comprises means for invoking an instance in said lower level.

11. The system of claim 9 wherein said means for invoking a lower level comprises means for invoking a plurality of instances in said lower level.

12. The system of claim 11 wherein said means for invoking a plurality of instances comprises means for concurrently invoking a plurality of instances.

13. A system for providing a hierarchical testing environment having a plurality of levels, comprising:

a task level driver having means for invoking a user task based upon data contained within a task file;

an intermediate driver, coupled to said task level driver, having means for invoking said task level driver based upon data contained within an intermediate file; and

a top level driver, coupled to said intermediate driver, having means for invoking said intermediate driver based upon data contained within a top level file.

14. A system of claim 13 wherein said top level driver creates a journal file based upon results of said intermediate file invocation.

15. A system for providing a hierarchical testing environment having a plurality of levels, comprising:

a task level driver having means for invoking a user task based upon data contained within a task file;

a first intermediate driver, coupled to said task level driver, having means for invoking said task level driver based upon data contained within a first intermediate file;

a second intermediate driver, coupled to said first intermediate driver, having means for invoking said first intermediate driver based upon data contained within a second intermediate file; and

a top level driver, coupled to said second intermediate driver, having means for invoking said second intermediate driver based upon data contained within a top level driver file.

16. A system of claim 15 wherein said top level driver creates a journal file based upon results of said intermediate file invocation.

17. A method for driving test cases, comprising the steps of:

reading instance attributes from a file;

placing any user defined attributes found in said file into system environment variables;

determining scenario driver configuration attributes for a current level;

executing begin hook code;

executing a next level driver based upon said instance attributes and said configuration attributes; and

executing end hook code.

18. The method of claim 17 further comprising the step of generating a report.

19. A system for driving test cases, comprising the steps of:

means for reading instance attributes from a file;

means for placing any user defined attributes found in said file into system environment variables;

means for determining scenario driver configuration attributes for a current level;

means for executing begin hook code;

means for executing a next level driver based upon said instance attributes and said configuration attributes; and

means for executing end hook code.

20. The system of claim 19 further comprising means for generating a report.