 |  |  |  |  |  |  |  |
| Version 8.0.1 |
The various SmartID features can be combined with each other. The following is the general syntax for combining SmartID features. Square brackets mark optional elements, while uppercase text signifies a placeholder:
#[%][noscope:][ENGINE:][CLASS:][VALUE][<INDEX>]
A SmartID consists of the following parts in the following order:
# always indicates the beginning of a SmartID.
% (optional) can mark VALUE as a regular expression (see Regular expressions).
noscope: (optional) can be used to indicate that the SmartID also applies outside of the current Scope.
ENGINE: (optional) specifies the UI engine to which the SmartID applies to. This is only needed if QF-Test is connected to multiple applications using different UI technologies at the same time. Valid values are: awt:, fx:, swt:, web:, and win:, whereby letter casing does not matter.
CLASS: (optional) specifies the generic class or class of the component (see chapter 60),
for example Label:, CheckBox:ComboBoxListItemCheckBox: or CheckBox\:MyCheckBox:.
VALUE (optional if CLASS is given) specifies the value the component must match, e.g. a label or name or the value of another criterium specified by MATCH.
<INDEX> (optional) specifies a numerical index, starting at 0.
Examples:
#Button:OK#TextField:Postal code<1>#TextField:name=address<2>#Postal code<1>#noscope:SWT:Label:Postal code<1> | | | | | | | Last update: 9/10/2024 Copyright © 1999-2024 Quality First Software GmbH |
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.
