Techniques for automated software testing

Patent metadata

Field	Value
Publication number	US-10013338-B2
Application number	US-201113816823-A
Country	US
Kind code	B2
Filing date	Sep 20, 2011
Priority date	Sep 24, 2010
Publication date	Jul 3, 2018
Grant date	Jul 3, 2018

Abstract

Described are techniques for testing an application. A test script including one or more instructions is received to test an application. A user interaction with a user interface of the application is emulated. Emulating includes executing a first portion of instructions in the test script. An output is received including information displayed using the user interface in response to the user interaction. Verification processing is performed for the output. The verification processing includes executing a second portion of instructions in the test script. A first instruction in the test script references a user interface data element without specifying a complete path for the user interface data element.

First claim

What is claimed is:

1. A method for testing an application comprising:
receiving a parameterized script including one or more testing parameters;
receiving test inputs including a set of one or more customized testing parameter values, said set including a corresponding customized testing parameter value for each of the one or more testing parameters;
generating, by a testing tool using a first set of inputs including the parameterized script and the test inputs, a test script including one or more instructions and the one or more customized testing parameter values used to test an application, wherein said generating includes substituting a corresponding customized testing parameter value from the set for each of the one or more testing parameters in the parameterized script;
verify, using said test script, one or more tests performed as part of qualification of a chromatography or mass spectrometry instrument;
verify, using said test script, first data displayed as a graph using a user interface, said first data being generated by said chromatography or mass spectrometry instrument in connection with performance testing of said chromatography or mass spectrometry instrument;
emulating a user interaction with the user interface of said application, said emulating comprising:
automating the user interaction with the user interface to test said application;
executing, based on the automated user interaction with the user interface, a first portion of said one or more instructions in said test script using the one or more customized testing parameter values also included in the test script to test the user interface of the application;
wherein the automated user interaction comprises setting one or more parameters of the chromatography or mass spectrometry instrument based on the one or more customized testing parameter values;
receiving, based on the executed first portion, an output including information displayed using said user interface in response to said emulated user interaction;

performing verification processing for said output, said verification processing including
executing a second portion of said one or more instructions in said test script, wherein a first instruction in said test script includes a partial path specification for a user interface data element, wherein user interface data elements are represented by nodes included in a hierarchy having at least three levels of nodes, said hierarchy including a root node at a first level of the hierarchy, said user interface data element being represented by a first node at another level of the hierarchy wherein a complete path for said user interface data element identifies a location of said user interface data element in said user interface by specifying a node at each level of the hierarchy from the root node at the first level to the first node at the another level, wherein said partial path specification in the test script includes said root node and a unique data element identifier for said user interface data element corresponding to the first node and wherein the partial path specification omits at least one other node of the complete path, said unique data element identifier uniquely identifying said user interface data element from other user interface data elements of the user interface; and
generating a report including results of said verification processing, said report including at least one image graphically illustrating said user interface provided as a result of executing said first portion of said one or more instructions, wherein said at least one image is generated as a result of the execution of said one or more instructions in said second portion.

2. The method of claim 1 , wherein said first node is a leaf in said hierarchy.

3. The method of claim 2 , wherein said partial path specification of the first instruction includes a window identifier corresponding to said root node at said first level.

4. The method of claim 3 , wherein said hierarchy includes four levels of nodes and said partial path specification omits identification of all levels other than a top level including said root node and a bottom level including the first node.

5. The method of claim 4 , further comprising:
searching for said user interface data element in said hierarchy, and wherein said first instruction includes criteria indicating a portion of the hierarchy to be excluded when searching for said user interface data element in said hierarchy.

6. The method of claim 3 , wherein said unique data element identifier is a name referenced by said application uniquely identifying said user interface data element from other user interface data elements.

7. The method of claim 1 , wherein said first instruction includes a parameter having a customized value supplied by a customer, wherein said test script is used for a first customer providing a first input for said parameter and a second customer providing a second input different from said first input for said parameter.

8. The method of claim 1 , wherein said test script is executed by the testing tool that communicates with said user interface and the method further comprising:
issuing a first request by said testing tool to said user interface for a handle to said user interface data element; and providing, by said user interface, said handle to said testing tool in response to said first request.

9. The method of claim 8 , further comprising:
issuing, by said testing tool to a first code module, a second request to retrieve said user interface data element using said handle;
issuing, by said first code module to said application, a third request to retrieve said user interface data element using said handle;
providing, by said application, first data including said user interface data element to said first code module in response to said third request; and
providing, by said first code module, said user interface data element to said testing tool.

10. The method of claim 9 , wherein said first code module processes said first data to generate said user interface data element in a format expected by said testing tool.

11. The method of claim 10 , wherein said user interface data element is a table of a plurality of data values.

12. The method of claim 10 , wherein said user interface data element is any of a row, a column or an element in a multi-dimensional vector.

13. The method of claim 1 , wherein the method is performed by a service provider to verify execution of said application on a computer system of a customer.

14. The method of claim 1 , wherein said test script is used to verify control settings of a device and data acquired using said device.

15. The method of claim 1 , wherein said test script is executed by the testing tool and the method further comprises:
performing first processing to obtain said user interface data element; and
verifying, by the testing tool, that the user interface data element matches expected output.

16. The method of claim 15 , wherein said first processing comprises: obtaining, by said testing tool from the user interface, a handle to the user interface data element;
issuing, by said testing tool to a library, a first request to obtain the user interface data element, wherein said first request is in accordance with a first application programming interface that includes the handle as a parameter; obtaining, by the library from the application, first data including the user interface data element; and responsive to the first request, returning the user interface data element from the library to the testing tool.

Assignees

• Leclair Steven
• Ramirez Enrique
• Yurach Dana
• Turner Laura
• Caswell Allen
• Robinson Mark
• Waters Technologies Corp

Inventors

• Leclair Steven
• Ramirez Enrique
• Yurach Dana
• Turner Laura
• Caswell Allen
• Robinson Mark

Classifications

• G06F11/3668 Primary

  Testing of software · CPC title

• G06F9/455

  Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines · CPC title

• G06F9/44

  Arrangements for executing specific programs · CPC title

• G06F11/3672 Primary

  Test management · CPC title