Checking an Object's State and Data in Android Open Applications

Basic Concepts

Checking an Object's State and Data in Keyword Tests

Checking an Object's State and Data in Scripts

If your mobile application is Open, to check whether a property or a method of a tested object returns the expected value, you can use special functionality provided by TestComplete - property checkpoints. They let you check whether a property or a set of properties of the tested application's object meet the specified conditions.

To check whether a control that displays data in a tabular form contains the correct data, you can use table checkpoints. Table checkpoints compare the actual data displayed by a control in your mobile application with the baseline data stored in your project. The baseline table must be stored in the Stores | Tables collection of your project. For information on how to work with table checkpoints, see About Table Checkpoints.

To check whether an object is displayed correctly, you can use region checkpoints. The region checkpoints obtain the actual image of the specified control and verify the image against the expected image of the object stored in the Stores | Regions collection in your project. Note that the region checkpoints allow you to set verification parameters - you can specify pixels to be treated as transparent and areas to be ignored during the verification. You can also command TestComplete to ignore slight differences between images. For more information on how region checkpoints work, see How Image Comparison Works.

You can create checkpoints during test recording and at design time when editing your test. For information on how to create checkpoints, see appropriate topics in the About Checkpoints section.

To check an object’s state in an Android Open Application in your keyword test, use the Property Checkpoint operation. For example, the Property Checkpoint operation in the keyword test shown in the image below checks whether a button is enabled.

Alternatively, you can use the If Object operation to quickly check an object’s state - whether the object exists, whether it is visible on screen or enabled. You can also create a custom verification procedure by using the If Then operation.

To check tabular data displayed by controls in your mobile application, use the Table Checkpoint operation. To check if an object in your mobile application is displayed correctly, use the Region Checkpoint operation.

The image below displays the Region Checkpoint operation that verifies that the control in a tested mobile application displays the correct data.

You can also use the Compare Picture operation or call methods TestComplete provides for image comparison (see Alternatives to Region Checkpoints for more information).

To check the state of an object in script tests, you can use the aqObject.CheckProperty method (this method is a scripting analog of the Property Checkpoint operation). It allows you to verify an object’s property against a condition:

def UseCheckProperty():
  Mobile.SetCurrent("MyDevice");
  # ...
  btnObj = Mobile.Device("MyDevice").Process("smartbear.example.demoapp").Layout("NO_ID").Button("addBtn");
  aqObject.CheckProperty(btnObj, "Enabled", 0, True);

Alternatively, you can use the if … then statement in your script test to check an object’s state:

def UseStoredTableNameCheck():
  Mobile.SetCurrent("MyDevice");
  # ...
  gridView = Mobile.Device("MyDevice").Process("smartbear.example.demoapp").Layout("NO_ID").GridView("gridView_Sample");
  Tables.BaselineTable.Check(gridView);

To check whether an object in an Android Open Application is displayed correctly in script tests, use the Regions.RegionCheckpoint.Check method (it is a scripting analog of the Region Checkpoint operation):

def UseRegionCheckpointCheck():
  Mobile.SetCurrent("MyDevice");
  # ...
  textView = Mobile.Device("MyDevice").Process("smartbear.example.demoapp").Layout("NO_ID").TextView("TextResult");
  Regions.TextResult.Check(textView);

Alternatively, you can use the Picture method to obtain the object’s image and then use one of the following methods to check whether the object is displayed correctly:

• Regions.Compare, Picture.Compare and Picture.Difference - Use these methods to compare the actual image of the object with the image stored in the Regions collection or with an arbitrary image.

• Regions.Find, Regions.FindRegion and Picture.Find - Use these methods to check whether the image of a tested object contains specified image or vice versa to check whether the image of the tested object belongs to the specified image.