Testing AIR Applications - Overview

General Notes on AIR Applications Testing

Approaches to Testing AIR Applications

Creating and Recording Tests for AIR Applications

About Test Types

About AIR Object Identification and Name Mapping

About Support for AIR Controls

Using Native AIR Methods and Properties in Testing

Viewing Object Properties and Methods

Where to Go Next

With TestComplete you can easily test AIR applications built with Flex or HTML. You can perform any kind of testing – unit, functional, regression and so on. The easiest way to create a test for your application is to record a keyword test or script routine. While replaying a test, TestComplete will repeat all of the recorded actions you performed with the tested AIR application during the recording. If necessary, you can also extend the recorded test manually using a number of specific features provided by TestComplete.

With TestComplete you can test AIR applications running under Adobe AIR version 2, 3 and 17.

In order to get access to an AIR application’s internals, you do not need to implement any specific interfaces or change your code in any way. You just need to prepare your application for testing. Once you have prepared your application, TestComplete exposes its objects automatically.

The way you can access application objects depends on the type of your AIR application:

Preparing HTML-Based AIR Applications for Testing

Preparing Flex-Based AIR Applications for Testing

With TestComplete, you can record and play back user actions in AIR applications, or you can create tests manually from scratch. Usually, it is easier to record the test first and then modify and enhance the recorded test.

When you record a test, you interact with the tested AIR application as an end-user would: navigate through the application’s screens, fill out forms and so on. TestComplete captures all actions you perform in the application and adds them to the test.

A test consists of a sequence of operations that define various interactions with objects in the tested application. For example, in the sample test below you can see that item selection from a combo box is represented by the ClickItem operation, clicking a button - by the ClickButton operation, and so on.

A sample keyword test recorded against an AIR application

def Test1():
  editorder = Aliases.Orders.wndOrders.editorderEditOrder;
  editorder.comboboxComboboxProduct.ClickItem("FamilyAlbum");
  textInput = editorder.textinputEditCname;
  textInput.Click(17, 10);
  textInput.Keys("John Smith");
  editorder.buttonBtnok.ClickButton;

The recorded tests can be modified and enhanced in a number of ways to create more flexible and efficient tests. For example, you can:

• Add new operations, reorder operations and modify their parameters.

• Delete or disable unneeded operations (for example, superfluous recorded operations).

• Insert checkpoints for verifying objects and values in the tested application.

• Create data-driven tests that run multiple test iterations using different sets of data.

Refer to the following topics to learn more about creating and enhancing tests:

There are two major test formats in TestComplete:

• Keyword tests - visually configured tests with grid-based editing interface. Best suited for novice users and those without programming knowledge.

• Scripts - code written in one of the supported scripting languages. May be better suited for advanced users.

You select the test type when creating a test and cannot change it later. However, you can mix keyword tests and scripts within the same test project and call them from each other.

TestComplete also includes additional test types, such as low-level procedures, unit tests, distributed tests and so on. You can use them to address specific testing needs. However, most automation is typically done using keyword tests and scripts.

Each object in an application has a number of properties, such as its location, text, type and so on. Some object properties are persistent and unchanging, and therefore can be used to locate objects in applications and differentiate among various objects.

When you record a test, TestComplete captures all windows and controls that you interacted with during the recording session and adds them to the Name Mapping project item (also known as the object repository or GUI map). For each captured object, TestComplete does the following:

• Selects a set of properties and values that uniquely identify the object in the application and saves them to Name Mapping as the object identification criteria. These properties will be used for locating the object during subsequent test recording, editing and run sessions.

• Generates an alias (name) that will be used to reference this object in tests. By default, TestComplete generates aliases based on object names defined in the application by developers.

• Automatically captures and adds images of the mapped objects to the Name Mapping repository. This helps you understand which window or control one or another mapped object matches.

The following image shows sample Name Mapping for a AIR application:

Here, the textinputEditCname object is identified via two properties - ObjectType and ObjectIdentifier. These properties specify the object’s accessible role and the object name as they are defined by the application developers in the application’s source code. However, AIR application objects can also be located by other properties, such as their class name, text and so on -- whatever best identifies a specific object.

If needed, you can modify the default Name Mapping generated by TestComplete. For example, you can:

• Change the identification properties and values to define more robust identification criteria or to reflect major GUI changes in newer versions of the tested application.

• Rename aliases to more meaningful and descriptive aliases, so that it is easier for you to understand which object is which.

• Manually add new objects to Name Mapping.

For more information, see Name Mapping.

Keep in mind that the object hierarchy in Name Mapping mirrors the object hierarchy in the tested application. When locating an object, TestComplete takes into account its entire parent hierarchy. If any object in the parent hierarchy cannot be found using the specified property values, the target object cannot be located as well. That is why it is important to select unique and unchanging properties for object identification.

TestComplete recognizes individual controls of AIR applications and lets you interact with them both at design time and while recording or replaying a test. In addition, it simplifies testing the user interface of your application since it includes a number of specific testing abilities for the most frequently used AIR controls.

For detailed information on what controls TestComplete provides extended support for and what abilities for testing applications’ controls it enables, see Support for AIR Applications' Controls.

TestComplete makes visual objects of Flex-based and HTML-based AIR applications available for testing, that is you can recognize these objects, interact with them and work with the following internal members of these objects:

• Public native properties and methods in Flex-based AIR applications.
• Public native properties in HTML-based AIR applications.

For detailed information on how to address exposed properties and methods from your tests, see Accessing Native Properties and Methods of AIR Objects and Addressing Objects in AIR Applications.

To see what operations (methods) are available for objects in your tested AIR application, as well as the object properties and their values, you can use the Object Browser or Object Spy. Available properties and methods include those provided by TestComplete, as well as native object properties and methods defined by the developers in the application’s source code.

You can view object properties and methods both at design time and at run time when the test is paused.

For more information on using the Object Browser, see Object Browser and Exploring Applications.

For further information about automating tests with TestComplete, refer to the following sections: