Assisted compositional reasoning for test scripts

• US 8,572,570 B2
• Filed: 06/10/2010
• Issued: 10/29/2013
• Est. Priority Date: 06/10/2010
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Grechanik, Mark, Xie, Qing, Fu, Chen
• Primary Examiner(s): DENG, ANNA CHEN
• Application Number:
  US12/813,405
• Publication Number:
  US 20110307864A1
• Time in Patent Office: 1,237 Days
• Field of Search: 717124-126
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable

Abstract

Assisted compositional reasoning for test scripts is implemented by a Type Inference of GUI Object References (TIGOR). TIGOR makes types of GUI objects explicit in the source code by using the properties of GUI objects as referred to in test script statements to access a GUI object repository for GUI objects that have matching GUI objects properties. TIGOR analyzes the GUI object types of the matching GUI objects in view of a sequence of operations performed on the GUI objects in the test script statements. TIGOR infers a GUI object type for a GUI object when that GUI object type is determined to be valid and/or compatible with a sequence of operations, such as API calls, executed in test script statements that perform actions on the GUI object.

Claims

1. A type checking method comprising:

analyzing, using logic executed by a processor, a test script statement stored in a non-transitory memory coupled to the processor to determine;

an exposed method expressed in the test script statement;

Application Programming Interface (API) calls, executable by the processor, characterized by API call types that navigate in sequence to the exposed method;

a destination Graphical User Interface (GUI) object that exposes the exposed method;

finding, using the logic executed by the processor, an element path between sequential GUI objects in a GUI tree, where the element path leads to the destination GUI object, where the sequential GUI objects are characterized by GUI object types;

determining, using the logic executed by the processor, whether the API call types in sequence are compatible with the GUI object types in sequence;

obtaining, from a GUI object repository, validated action result for actions performed by the API calls on GUI object types in sequence;

assigning API call types to each API call according to the action results that specify valid API calls useable to perform actions on particular GUI object types;

obtaining, from the GUI object repository, mappings of GUI object types, where each of the mappings comprise properties of a GUI object type;

assigning GUI object types to each GUI object according to the API call types in sequence determined to be compatible with the GUI object types in sequence;

determining a GUI object interactions count for the sequential GUI objects based on a configurable number of GUI object interactions for the sequential GUI objects; and

generating a type inferencer message guide that explain how to transform data during data exchange between the GUI object.

2. The method of claim 1, further comprising:

finding multiple GUI object interaction paths that perform actions on the sequential GUI objects;

validating useable GUI object interaction paths from the multiple GUI object interaction paths that control the actions performed on the sequential GUI objects; and

determining a number of GUI object interactions in each of the useable GUI object interaction paths.

3. The method of claim 2, further comprising:

selecting from the useable GUI object interaction paths, a first path selected having the least number of GUI object interactions of the useable GUI object interaction paths.

4. The method of claim 2, further comprising:

selecting from the useable GUI object interaction paths, a first path selected having the greatest number of GUI object interactions of the useable GUI object interaction paths.

5. The method of claim 2, further comprising:

determining the type of the exposed method in the useable GUI object interaction paths, where the useable GUI object interaction paths each extend from a root node representing the destination GUI object that exposes the exposed method, the top container window, or both.

6. The method of claim 1, where the test script statement references GUI objects using the properties of the GUI objects, the GUI objects properties comprising:

name;

location;

color;

size, or any combination thereof.

7. A product, the product comprising:

a non-transitory machine-readable medium;

logic, stored on the machine-readable medium, that when executed by a processor, cause the processor to;

analyze a test script statement to determine;

an exposed method expressed in the test script statement;

Application Programming Interface (API) calls, executable by the processor, characterized by API call types that navigate in sequence to the exposed method;

determine a destination Graphical User Interface (GUI) object that exposes the exposed method;

find an element path between sequential GUI objects in a GUI tree, where the element path leads to the destination GUI object, where the sequential GUI objects are characterized by GUI object types;

determine whether the API call types in sequence are compatible with the GUI object types in sequence;

obtain, from a GUI object repository, validated action result for actions performed by the API calls on GUI object types in sequence;

assign API call types to each API call according to the action results that specify valid API calls useable to perform actions on particular GUI object types;

obtain, from the GUI object repository, mappings of GUI object types, where each of the mappings comprise properties of a GUI object type;

assign GUI object types to each GUI object according to the API call types in sequence determined to be compatible with the GUI object types in sequence;

determine a GUI object interactions count for the sequential GUI objects based on a configurable number of GUI object interactions for the sequential GUI objects; and

generate a type inferencer message guide that explain how to transform data during data exchange between the GUI object.

8. The product of claim 7, where the logic to find multiple GUI object interaction paths, that when executed by a processor, further causes the processor to:

validate useable GUI object interaction paths from the multiple GUI object interaction paths that control the actions performed on the sequential GUI objects; and

determine a number of GUI object interactions in each of the useable GUI object interaction paths.

9. The product of claim 8, where the logic further causes the processor to:

select from the useable GUI object interaction paths, a first path selected having the least number of GUI object interactions of the useable GUI object interaction paths;

or some combination of GUI object interactions of the useable GUI object interaction paths.

10. The product of claim 8, where the logic further causes the processor to:

select from the useable GUI object interaction paths, a first path selected having the greatest number of GUI object interactions of the useable GUI object interaction paths;

or some combination of GUI object interactions of the useable GUI object interaction paths.

11. The product of claim 8, where the logic further causes the processor to:

determine the type of the exposed method in the useable GUI object interaction paths, where the useable GUI object interaction paths each extend from a root node representing the destination GUI object that exposes the exposed method.

12. The product of claim 7, where the test script statement references GUI objects using the GUI objects properties of the GUI objects, the properties comprising:

name;

location;

color;

size, or any combination thereof.

13. A system, the system comprising:

a processor;

a memory coupled to the processor, the memory comprising;

a test script statement, comprising;

an exposed method expressed in the test script statement;

Application Programming Interface (API) calls characterized by API call types that navigate in sequence to the exposed method;

logic, stored in the memory, that when executed by the processor, causes the processor to;

determine a destination Graphical User Interface (GUI) object that exposes the exposed method;

find an element path between sequential GUI objects in a GUI tree, where the element path leads to the destination GUI object, where the sequential GUI objects are characterized by GUI object types;

determine whether the API call types in the element path between sequential GUI objects are compatible with the GUI object types in the sequence;

obtaining, from a GUI object repository, validated action result for actions performed by the API calls on GUI object types in sequence;

calculating API call type assignments for each API call according to the action results that specify valid API calls useable to perform actions on particular GUI object types;

obtaining, from the GUI object repository, mappings of GUI object types, where each of the mappings comprise properties of a GUI object type;

assigning GUI object types to each GUI object according to the API call types in sequence determined to be compatible with the GUI object types in sequence;

determining a GUI object interactions count for the sequential GUI objects based on a configurable number of GUI object interactions for the sequential GUI objects; and

generating a type inferencer message guide that explain how to transform data during data exchange between the GUI object.

14. The system of claim 13, where the logic further causes the processor to:

find multiple GUI object interaction paths that identify API calls that perform actions on the sequential GUI objects;

validate useable GUI object interaction paths from the multiple GUI object interaction paths that control the actions performed on the sequential GUI objects; and

determine a number of GUI object interactions in each of the useable GUI object interaction paths.

15. The system of claim 14, where the logic further causes the processor to:

select from the useable GUI object interaction paths, a first path selected having the least number of GUI object interactions of the useable GUI object interaction paths.

16. The system of claim 14, where the logic further causes the processor to:

select from the useable GUI object interaction paths, a first path selected having the greatest number of GUI object interactions of the useable GUI object interaction paths.

17. The system of claim 14, where the logic further causes the processor to:

determine the type of the exposed method in the useable GUI object interaction paths, where the useable GUI object interaction paths each extend from a root node representing the destination GUI object that exposes the exposed method.

18. The system of claim 13, where the test script statement references GUI objects using the properties of the GUI objects, the GUI objects properties comprising:

name;

location;

color;

size, or any combination thereof.