Control properties

There are various types of control properties, which are described in this chapter.

You can use control properties as identification parameters to identify objects, or to steer controls by defining the Value column in the test case.

Business properties

Tosca Cloud provides business properties that you can use with specific control types. These properties are consistent across all technologies to be steered.

Each control type in GUI and NonGUI applications includes the business properties Exists and ResultCount.

  • The property Exists indicates whether a control exists or not (True or False).

  • The property ResultCount indicates how often the current node exists.

Each control type of GUI applications contains the business properties Enabled, IsSteerable, and Visible.

  • The property Enabled indicates whether a control is enabled (True) or disabled (False).

  • The property IsSteerable indicates whether a control can be edited or not.

  • The property Visible indicates whether a control is visible or not.

Technical properties

Technology-specific properties are based on the underlying technology and they are read out from the application. For example, every HTML element has a Tag property.

Reflected properties

All properties of an identified element in the test object can be retrieved via reflected access at runtime, provided that the target technology supports this. This can be done in Tosca XScan via the option Get all properties.

You can use properties retrieved through reflective access for verification processes and control identification, but you cannot use the action mode Input.

Default properties

In Tosca Cloud, some controls use a default property in case no property is selected in the test step value. You can use these control properties to perform verifications on your control.

For more information about default properties for a specific control, check the details provided for that control type.

Verifying properties

Control properties are verified by using the Value column and the following syntax <Property><Operator><Value>.

If you want to use the default property, enter the syntax <Operator><Value>.

Syntax description:

.<Property>

Name of the control property using a dot as a prefix. Which properties are available depends on the technology used and the control to be steered.

Example: .enabled, .exists, .value

<Operator>

Possible operators: ==, !=, >, <, <=, >=

<Value>

The value that must be specified in order to fulfill a condition.

Possible values: True, False, <value> (alphanumeric)

You can enter the syntax directly into the Value column, or you use the input assistant described below.

  1. Set the value of the Action mode column to Verify, WaitOn, Select or Constraint.

  2. Define the according data type.

  3. Click onto the blue arrow in the Value column to open the input assistant for entering the syntax.

  1. Select the property without any prefix and the operator from the according drop-down lists. The operators are provided depending on the context. Whenever you modify either the action mode or the data type, Tosca Cloud will automatically apply the default operator.

  2. Enter the value to be verified into the input field right next to the operator.

Make sure to use an appropriate data type for your verification.

For instance, if you verify for the property Exists, the data type should be Boolean. data types Numeric and Date are interpreted as a number and a date, respectively.