Property Checkpoint Operation

Applies to TestComplete 15.69, last modified on November 13, 2024

Description

Add the Property Checkpoint operation to your keyword test to verify the property value of an object in the tested application. When you add the operation to your test, TestComplete displays the Checkpoint wizard that assists you in setting up the checkpoint parameters. To modify the checkpoint’s parameters, double-click the operation in the Keyword Test editor.

Operation Result

If the property value matches the specified condition, the operation returns True and posts a checkpoint message () to the test log. Otherwise, the operation returns False and posts an error message () to the log.

Scripting Analogue

The operation is analogue to the aqObject.CheckProperty scripting method.

Child Operations

The operation cannot have child operations.

Operation Parameters

The operation has the following parameters:

Object

The object whose property you want to check.

Property

The name of the property to be checked.

If the property with the given name is not found, an error occurs. Use the aqObject.IsSupported method to verify whether the object has a specific property.

Condition

Specifies the condition that will be used to compare a property value with the Value parameter.

Notes:

  • When testing a property value of a string type, you can use any of these conditions. For more information about string comparison rules, see the Remarks section.

  • If you select the Matches or Not Matches condition, the property value will be compared with the regular expression specified by the Value parameter.

  • When testing a numeric property value, you can use any of the following conditions: Equals, Does not equal, Greater than, Less than, Greater than or equal to, Less than or equal to.

  • When testing a property that has a Boolean value, you can use only the Equals or Does not equal condition.

Value

Specifies the value to test the property value against. The meaning of this parameter depends on the Condition parameter (see the table above).

CaseSensitive

If Value is string, this parameter specifies whether the operation should perform case-sensitive or case-insensitive comparison; otherwise, this parameter is ignored. By default, this parameter is True, which means case-sensitive comparison; False means that the letter case is ignored.

To modify operation parameters:

  1. Select the needed operation in your keyword test.

  2. Click the Value cell twice (not double-click) or select the cell and press F2. This will activate the in-place editor.

  3. Click the ellipsis button of the in-place editor. TestComplete will open the Operation Parameters dialog.

  4. In the dialog, specify the operation parameters. For detailed information on how to work with the dialog, see Specifying Operation Parameters.

  5. Click OK to close the dialog and apply changes.

  6. Press Enter to confirm the changes and close the in-place editor, or press Esc to close the editor discarding any changes.

Remarks

  • By default, if the Property Checkpoint operation cannot find or access the object, the property of which it verifies, it waits for the object for a period that the Playback > Auto-wait timeout property of your project specifies. If the object has not been found by the end of the period, the operation fails.

  • String comparisons ("equals to", "greater than", "less than" and similar) use character codes and are not affected by the locale. For example, "b" is greater than "a", "c" is greater than "b" and so on. If the CaseSensitive parameter is True, letter case is taken into account ("a" is greater than "A"), otherwise it is ignored ("a" is equal to "A"). The comparison is performed symbol-by-symbol and finishes once a difference is found or when both strings have been compared to the end. If two strings having different lengths compare as equal to the end of one string, the longer string is considered as the greater one. For instance, "abcd" is greater than "ab".

  • You can use the cmpIn and cmpNotIn conditions to test a property’s actual value against comma-separated, pipe-separated lists, and so on, that is, to check whether the actual value equals (or does not equal) to any value stored on the list. For example, you can use the cmpIn condition to check whether the script selected in the Script box of the Notepad’s Font dialog equals to one of the values contained in the "Western|Central European" list.

See Also

Checkpoints Category
About Property Checkpoints
Alternatives to Property Checkpoints
Checkpoint Wizard
Specifying Operation Parameters
Checking Operation Result

Highlight search results