Using Keyword Tests for Data-Driven Testing

Retrieving Data and Iterating Through Storage

Entering Data Into an Application’s Form

Verifying Test Action Results

Web Article

Using the Data-Driven Loop Operation

Using Scripting Methods and Routines

To enter data into application forms and controls, you either simulate keystrokes or mouse clicks, or store the desired value directly to a property of the desired form or control.

In many cases, the easiest way to understand how to simulate the appropriate input is to record a test using one portion of test data and see how TestComplete does this. You can then modify this test so that it assumes input data as parameters.

The following notes may help you with creating a test that simulates user input:

• To simulate a key press, use the On-Screen Action operation that calls the Keys method of a tested window or control.

• To set a value in a text box, use the On-Screen Action operation that calls the SetText action or change the wText property value of this text box.

• To simulate mouse actions over list boxes, combo boxes, tree views, list views and other controls, use specific methods of these objects. See Working With Application Objects and Controls.

• If your tested application is compiled as an Open Application, you may call methods defined by the application code or assign values directly to properties of application’s internal objects. To call the methods and assign properties, you can use the On-Screen Action, Call Object Method and Run Code Snippet operations.

• To change the type of the data you retrieve from a storage, use the VarToStr or VarToInt method. See Retrieving Input Data From Storage.

For information on simulating user input, see also Simulating User Actions.

To verify that the tested application works as expected, you compare the application’s output with some expected values. For instance, if you test an Edit Order form, you may check that the total sum of an order is calculated with the appropriate discounts.

A good practice is to store the baseline values along with the test data in the data storage and use the baseline value for each portion of test data (that is, for each row). See Organizing Data Storages.

To compare data and values we recommend that you use TestComplete checkpoints. If the output is an image, file or database table, you can use checkpoints of the appropriate type to compare images, files and data tables. To compare individual property values, you can also use the If... Then and Else operations.

Our web site has an article that describes how to use keyword tests to create data-driven tests in TestComplete:

Introduction to Data-Driven Testing in TestComplete