Method for Signaling Runtime Events to an Automated Test Script

• US 20080109794A1
• Filed: 11/07/2006
• Published: 05/08/2008
• Est. Priority Date: 11/07/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Malasky, Bruce A., Adams, Cheryl S., Havin, Victor L.
• Application Number:
  US11/557,167
• Publication Number:
  US 20080109794A1
• Time in Patent Office: Days
• US Class Current: 717/130
• CPC Class Codes: G06F 11/3672 Test management

Abstract

An embodiment of the present invention relates to using a test script to test a program under test (PUT) based on instrumenting the program under test by inserting state inspection code into predefined points of interest associated with test initialization points, test start points, and test completion points. A test script is modified to listen for notifications from the instrumented program under test. When an instrumented process is being executed notification is sent to a runtime library (RTL). The runtime library then delivers the notification by way of inter-process communication (IPC) to the test script. The test script uses such notifications, in part, to determine states of the program under test and to test the program under test.

Claims

1. A method of signaling runtime events to an automated test script, said method comprising:

instrumenting a program under test (PUT) by adding code at a plurality of points of interest;

acquiring references to a runtime library in said plurality of points of interest;

modifying a test script to listen for notifications from said program under test;

modifying the launching procedure to cause said program under test to run;

sending notification from said program under test to said runtime library when one of said plurality of points of interest is executed; and

signaling runtime events using inter-process communications (IPC) to send notifications from said runtime library to said test script.

2. The method in accordance with claim 1, wherein instrumenting a program under test includes instrumenting said program under test by inserting a plurality of state inspection code into said plurality of points of interest.

3. The method is accordance with claim 2, wherein said plurality of points of interest include test initialization points, test start points, and test completion points.

4. The method is accordance with claim 3, wherein said test script is part of an automated test system.

5. The method in accordance with claim 4, wherein instrumenting a program under test includes using a code instrumentation engine.

6. The method in accordance with claim, 5 wherein said test script does not contain any delays and or pre-calculated timeouts.

7. The method in accordance with claim 6 wherein, said points of interest are determined by a test engineer.

8. The method is accordance with claim 7, wherein said program under test is firmware.

9. The method in accordance with claim 8, wherein said probe kit is an IBM BCI probe kit.

10. The method in accordance with claim 9, wherein said method does not make use of a debugger.

11. The method is accordance with claim 7, wherein said program under test is a Java program.

12. The method in accordance with claim 11, wherein said probe kit is an IBM BCI probe kit.

13. The method in accordance with claim 12, wherein said method does not make use of a debugger.

14. The method is accordance with claim 4, wherein said automated test system is a rational functional tester (RFT).

15. The method in accordance with claim 5, wherein said code instrumentation engine is a probe kit (PK).