Automated testing

• US 20040153837A1
• Filed: 09/11/2003
• Published: 08/05/2004
• Est. Priority Date: 09/13/2002
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Preston, Adrian James, Stewart, James Clive
• Application Number:
  US10/660,011
• Publication Number:
  US 20040153837A1
• Time in Patent Office: Days
• US Class Current: 714/39
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A system for recording for reuse, at least one test event and at least one associated response. A testing program sends one or more test events (e.g. button click) to a component (e.g. a web browser software application) and receives an associated response from the component (e.g. associated button is clicked). A tracing program stores test events and responses in a trace file and an analyser program analyses the file and creates “situations” of test events and associated responses. If required, the situations are further processed by an extractor program, which extracts surplus test events that are not required in order to produce an associated response. This extracting process produces a minimum set of test events, and the minimum sets and associated response are stored for reuse.

Claims

1. A system for recording for reuse, at least one test event and at least one associated response, said system comprising:

an application program for testing at least one function of a component to be tested;

a communication protocol for sending by said application program, said at least one test event to said component and receiving from said component, said at least one associated response;

storage for storing by a tracer, said at least one test event and said at least one associated response, in a trace file;

an analyser for analysing said trace file;

an extractor for extracting at least one minimum set of test events from said trace file, wherein said at least one minimum set generates said at least one associated response; and

said storage being further adapted to store said at least one minimum set and said at least one associated response.

2. A system as claimed in claim 1, in which said analyser comprises means for determining whether said trace file is empty.

3. A system as claimed in claim 1, in which said analyser comprises means for parsing said at least one test event.

4. A system as claimed in claim 1, in which said analyser comprises means for creating at least one reusable program comprising said at least one minimum set and said at least one associated response.

5. A system as claimed in claim 4, in which said analyser comprises means for adding said at least one reusable program to said storage.

6. A system as claimed in claim 1, in which two or more reusable programs share said at least one test event.

7. A system as claimed in claim 6, in which if said shared at least one test event generates two or more associated responses, said system further comprises means for invoking a rule for logging one of said two or more reusable programs.

8. A system as claimed in claim 1, in which said component to be tested is at least one of a hardware component or a software component.

9. A method for recording for reuse, at least one test event and at least one associated response, for use in a system comprising:

an application program for testing at least one function of a component to be tested, said method comprising the steps of;

sending by said application program, said at least one test event to said component and receiving from said component, said at least one associated response;

storing said at least one test event and said at least one associated response in a trace file;

analysing said trace file;

extracting at least one minimum set of test events from said trace file, wherein said at least one minimum set generates said at least one associated response; and

storing said at least one minimum set and said at least one associated response.

10. A method as claimed in claim 9, in which said analysing step further comprises a step of determining whether said trace file is empty.

11. A method as claimed in claim 9, in which said analying step further comprises a step of parsing said at least one test event.

12. A method as claimed in claim 9, in which said analysing step further comprises a step of creating at least one reusable program comprising said at least one minimum set and said at least one associated response.

13. A method as claimed in claim 12, in which said analysing step further comprises a step of adding said at least one reusable program to said storage.

14. A method as claimed in claim 9, in which two or more reusable programs share said at least one test event.

15. A method as claimed in claim 14, in which if said shared at least one test event generates two or more associated responses, said method further comprises a step of invoking a rule for logging one of said two or more reusable programs.

16. A method as claimed in claim 9, in which said component to be tested is at least one of a hardware component or a software component.

17. A computer program comprising program code means adapted to perform all the steps of claim 9 when said program is run on a computer.