Data structures for use with environment based data driven automated test engine for GUI applications

• US 20030052917A1
• Filed: 09/14/2001
• Published: 03/20/2003
• Est. Priority Date: 09/14/2001
• Status: Active Grant

• Current Assignee: RingCentral Incorporated
• Original Assignee: Siemens Communications Incorporated (Siemens AG)
• Inventors: Dubovsky, David
• Granted Patent: US 6,948,152 B2
• Time in Patent Office: Days
• US Class Current: 345/764
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

The invention relates to data structures for use with an environment based data driven test engine for computer programs which have a graphical user interface (GUI). The data structures are used in connection with a scriptable GUI test tool. The tool generates a GUI map (or includes a utility which generates a GUI map), at least one environment definition (parameter) file, at least one test data (driver) file, and an automated test engine. A separate environment definition file is provided for each feature of the GUI. Each environment definition file provides the abstract details required by the test engine in order to support common processes for different applications. The test data file is organized into rows of data where each row defines a single test and each column represents a parameter. The automated test engine is composed of a plurality of library modules written in the scripting language of the scriptable GUI test tool. The ATE is driven by the test data file and calls upon the GUI map and environment definition file. According to the presently preferred embodiment, the scriptable GUI test tool is WinRunner®. The environment definition files and the test data files are preferably generated with a spreadsheet program such a Microsoft Excel® and saved as comma delimited text files.

Claims

1. A data structure for use with a graphical user interface (GUI) test tool to test a software application having a GUI with different application objects, said data structure comprising:

a) an environment part, said environment part including Application Name, Launch Menu, Primary Window identification, Tab and related tab windows; and

b) a parameters part, said parameters part including individual fields that appear in an application object.

2. The data structure according to claim 1, wherein:

said individual fields include a “

type”

definition.

3. The data structure according to claim 1, wherein:

parameter elements that are new to a specific version of an application are identified.

4. The data structure according to claim 1, wherein:

values found in the data structure are tightly bound to logical names that are used in a GUI map.

5. The data structure according to claim 1, wherein:

the data structure is organized in rows and columns.

6. The data structure according to claim 5, wherein:

the data structure is a comma delimited text file.

7. The data structure according to claim 5, wherein:

the data structure is a spreadsheet file.

8. A data structure for use with a graphical user interface (GUI) test tool to test a software application having a GUI with different application objects, said data structure comprising:

a plurality of rows, each row containing a plurality of columns, each row defining a single test and each column representing a parameter.

9. The data structure according to claim 8, further comprising:

multiple rows of data to facilitate or verify the results of an individual test.

10. The data structure according to claim 9, wherein:

each of said multiple rows of data begins with a first line of data containing a definition of default values that are expected for each parameter.

11. The data structure according to claim 10, wherein:

said first line of data is followed by one or more rows of individual data driven tests.

12. The data structure according to claim 11, wherein:

each of said one or more rows includes standard fields and data specific for each field of an object being tested.

13. The data structure according to claim 12, wherein:

said standard fields include a Test ID, Preamble a nd Postamble action, Expected Result indication and a Comment.

14. The data structure according to claim 12, wherein:

Preamble and Postamble actions are application specific and represent user actions required to establish a starting point for a test and an action to perform to execute a desired test.

15. The data structure according to claim 13, wherein:

said expected result field indicates whether a test will pass completely or fail during data entry, during the execution of the postamble or during verification after the postamble action has been executed.

16. The data structure according to claim 13, wherein:

data that appears in individual fields of a data driven test are specific for a parameter, operation or use of said field.

17. The data structure according to claim 16, wherein:

at least one of said fields includes an indication selected from the group consisting of ignored, changed, left alone and ignored for Query operations.

18. The data structure according to claim 17, wherein:

data represents multiple columns of a table structure.

19. The data structure according to claim 8, wherein:

the data structure is generated with a spreadsheet program and saved as comma delimited text files.

20. A test script for use with a scriptable test tool for testing the graphical user interface (GUI) of a software application comprising:

a plurality of library modules written in the scripting language of the scriptable GUI test tool,

said library modules including a file which contains functions to handle the PreAmble and PostAmble actions of the test cases.

21. A test script according to claim 20, wherein:

said library modules includes a file which contains general functions that are always application specific.

22. A test script according to claim 20, wherein:

said library modules includes a file which contains functions for all common procedure test cases and which controls the main flow and logic for testing.

23. A test script according to claim 20, wherein:

said library modules includes a file which contains miscellaneous functions to handle loading of GUI map files, opening of the specific test object, file I/O and several wait functions required during test execution.

24. A test script according to claim 20, wherein:

said library modules includes a file which is loaded automatically by said scriptable test tool and which initializes physical GUI recognition parameters that have been carefully defined for the application.

25. A test script according to claim 20, wherein:

said library modules includes a file entitled which has two functions which are used to handle field value assignment and validation based on input data.

26. A test script according to claim 20, wherein:

said library modules includes a file which varies between testers at each different test site and contains several global variable definitions that allow an individual tester to specify alternate parameters and characteristics that may be unique to a location and or purpose of a test.

27. A test script according to claim 20, wherein:

said library modules includes a file which defines all global variables.

28. A test script according to claim 20, wherein:

said library modules includes a file which provides parameter Set and Check functions.

29. A test script according to claim 20, wherein:

said library modules includes a file entitled which provides an interface between individual Batch files and a test engine.

30. A test script according to claim 20, wherein:

said library modules includes a file which declares and initializes global variables that are application specific for recognition and processing of user actions.

31. A test script according to claim 20, wherein:

said library modules includes a file which uses as input a Parameter File for an Object Under Test.

32. A test script according to claim 20, wherein:

said library modules includes a file which contains functions that are specific to dealing with pop-up windows that are presented to a user during the course of the operation of the application under test.