Test and verification framework

• US 7,185,235 B2
• Filed: 11/27/2002
• Issued: 02/27/2007
• Est. Priority Date: 12/28/2001
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Radestock, Guenter
• Primary Examiner(s): Beausoliel; Robert
• Assistant Examiner(s): PUENTE, EMERSON C
• Application Number:
  US10/306,797
• Publication Number:
  US 20030126521A1
• Time in Patent Office: 1,553 Days
• Field of Search: 714 28- 33, 714/47, 709/223, 709/224, 717/124
• US Class Current: 714/47.1
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

Systems and techniques to test a software product in one or more computer systems. In general, in one implementation, the technique includes calling components in a first computer system during execution of a test, recording the calls, and rerunning the recorded calls in a second computer system in order to recreate the behavior of the first computer system during execution of the test.

Claims

1. A method for performing a test comprising:

calling at least one of a plurality of components in a first computer system during execution of a test, each of said components configured with a trace feature that when called enables writing to a trace file during the test;

for each of said at least one of the plurality of components called, writing a command associated with said component to the trace file, the command being operative to call said component when executed;

executing the commands in the trace file at a second computer system;

calling said at least one of the plurality of components in the second computer system;

obtaining a first result from executing the test on the first computer system;

obtaining a second result from calling the plurality of components in the second computer system; and

comparing the first result and the second result.

2. The method of claim 1, wherein said plurality of components comprise components in an Application Programming Interface (API) layer.

3. The method of claim 1, wherein said plurality of components comprise at least one component in the test layer.

4. The method of claim 1, wherein said writing a command comprises writing a script to the trace file.

5. A system comprising:

a trace file;

a plurality of Application Programming Interface (API) components residing on a first computer system and a second computer system, at least one API component including a trace feature operative to write a command comprising a script to the trace file when the API component is called during a test;

a plurality of test component residing on the first computer system and the second computer system, at least one test component including a trace feature operative to write a command comprising a script to the trace file when the test component is called during the test; and

a comparison unit operative to obtain a first result from executing the test on the first computer system, obtain a second result from an execution of the scripts in the trace file in the second computer system, and compare the first result and the second results.

6. The system of claim 5, wherein the command is operative to call the component associated with the trace feature that wrote the command.

7. An article comprising a machine-readable medium storing instructions operable to cause one or more machines to perform operations comprising:

calling at least one of a plurality of components in a first computer system during execution of a test, each of said components configured with a trace feature that when called enables writing to a trace file during the test;

for each of said at least one of the plurality of components called, writing a command associated with said component to the trace file, the command being operative to call said component when executed;

executing the commands in the trace file at a second computer system;

calling said at least one of the plurality of components in the second computer system;

obtaining a first result from executing the test on the first computer system;

obtaining a second result from calling the plurality of components in the second computer system; and

comparing the first result and the second result.

8. The article of claim 7, wherein said components comprise components in an Application Programming Interface (API) layer.

9. The article of claim 7, wherein said components comprise components in a test layer.

10. The article of claim 7, wherein said writing comprises recording said calls as a script to a trace file in response to one of the components being called.

11. The article of claim 10, wherein the script comprises a command operative to call said one of the components when executed.

12. The article of claim 11, wherein said executing comprises rerunning the recorded calls by executing scripts in the trace file.

13. A method comprising:

initiating a first test on a software product in a first computer system;

calling Application Programming Interface (API) components, each of said API components configured with a trace feature that when called enables writing to a trace file;

writing a script to the trace file for at least one API component called during the test, the script being operative to call a corresponding component when executed;

obtaining a first result from the first test;

executing the scripts in the trace file to initiate a second test on a software product in a second computer system;

obtaining a second result from the second test; and

comparing the first and second results;

wherein the first computer system is separate and distinct from the second computer system.

14. The method of claim 13, wherein the scripts comprise Python scripts.

15. An apparatus comprising:

means for calling a plurality of components in a first computer system during execution of a test, each of said components configured with a trace feature that when called enables writing to a trace file during the test;

means for writing a command associated with said component command to the trace file for each of at least one of the plurality of components, the command being operative to call said component when executed;

means for executing the commands in the trace file at a second computer system;

means for calling said at least one of the plurality of components in the second computer system;

means for obtaining a first result from executing the test on the first computer system;

means for obtaining a second result from calling the plurality of components in the second computer system; and

means for comparing the first result and the second result.

16. An apparatus comprising:

means for initiating a test on a software product in a first computer system;

means for calling Application Programming Interface (API) components, each of said API components configured with a trace feature that when called enables writing to a trace file during the test;

means for writing a script to the trace file for at least one API component called during the test, the script being operative to call a corresponding component when executed;

means for obtaining a result from the test;

means for executing the scripts in the trace file in a second computer system;

means for obtaining a result from executing the scripts in the second computer system; and

means for comparing the results obtained in the first computer system to the results obtained in the second computer system.