Generic classes

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:

It is possible to record additional component recognition features, depending on the generic class. Often, depending on the generic class, it makes sense to change the recorded 'Feature' and/or the recorded 'Extra features', e.g. the qfs:label.
Depending on the generic class, class specific checks may be provided, e.g. the check to check a complete table row if the generic class equals Table.
The indexing of sub-elements during recording, this means that e.g. during click recording on a table cell only a 'Component' for the table gets recorded, while the exact cell is referenced via indices.
The recording of the generic type, as far as reasonable.
With generic classes it becomes decidable whether the exact position or the most suitable position should get record for mouse clicks.
Simply by assigning a recorded component to a generic class, component recognition gets sharpened compared to non-specific HTML classes.

The following sections list which information is saved in particular.

Last update: 9/10/2024
Copyright © 1999-2024 Quality First Software GmbH

Cookie configuration

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.

Activate Matomo-Cookies Activate Matomo-Cookies

Confirm selection

Name

Provider

Lifetime

Type

Name

_pk_id

Provider

Matomo

Lifetime

13 months

Type

HTTP

Description

This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.

Name

_pk_ref

Provider

Matomo

Lifetime

6 months

Type

HTTP

Description

This cookie is used to track from which website the anonymized user proceeded to our website.

Name

_pk_ses

Provider

Matomo

Lifetime

1 day

Type

HTTP

Description

The Matomo session cookie is used to track the visitor's page requests during the session.

Name

_pk_testcookie

Provider

Matomo

Lifetime

Session

Type

HTTP

Description

is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).

Name

_pk_cvar

Provider

Matomo

Lifetime

30 Min

Type

HTTP

Description

short lived cookies used to temporarily store data for the visit.

Name

_pk_hsr

Provider

Matomo

Lifetime

30 Min

Type

HTTP

Description

short lived cookies used to temporarily store data for the visit.

4.0+60Generic classes

4.0+60
Generic classes