 |  |  |  |  |  |  |  |
| Version 7.1.3 |
Geometry only has a small part in component recognition if other criteria are available. It also is possible for a component to neither have a name, nor a label or usable extra features or index. If then even an application-specific resolver (see section 52.1) cannot provide any recognition criteria, the recognition will rely on the component class (which is always available), the component hierarchy, and position and size of the component.
If in this case you take care that the window sizes during replay are the same as during recording (see 'Component event'), the component recognition should be stable. However, the modification effort for version changes of the application can be somewhat higher, since position changes of components must be explicitly traced.
| | | | | | | Last update: 4/23/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.
