Version 8.0.1 |
QF-Test abstract recorded class from the framework specific classes in order to get classes of common use. Those classes are called generic classes. This concept provides a better readability and clearer understanding of components. Furthermore already created tests can be re-used once the target technology is switched or if you want to maintain tests in various technologies in parallel.
Beside those generic classes QF-Test records generic types as well.
Those types give a more detailed specification of the target
component. A typical use case are password fields. Those fields have the
generic class TextField
, but they have that specific
characteristic to enter passwords, so they get an additional generic
type TextField:PasswordField
.
Using those types makes the recognition of generic classes for certain
categories stricter and more appropriate.
A great advantage of these generic classes, especially when testing web applications is that a user can freely assign these generic classes to components. Later on these mappings may get reduced onto other generic classes. An example how this can be done may be found in the manual chapter 'CustomWebResolver' – Tables.
Using generic classes has the following advantages:
qfs:label
.
Table
.
The following sections list which information is saved in particular.
Last update: 9/10/2024 Copyright © 1999-2024 Quality First Software GmbH |
1. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
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.