Si vous ne trouvez pas ce que vous cherchez, essayez encore une fois avec des "guillemets", par exemple "windows 10" au lieu de windows 10. Plus d'informations sur la recherche
Version 5.4.1 28.4.1 Behavior-Driven Testing (BDT) from technical perspective Describing a test-case from a technical perspective using Behavior-Driven Testing (BDT) uses more or less elementary actions for designing a test-case. You can find a sample test-suite at qftest-5.4.1/demo/keywords/behaviordriven/BehaviorDrivenTesting.qft. The respective test-plan can be found at…
Version 6.0.4 48.1.4installCustomWebResolver - Samples When defining a CustomWebResolver you can use one of the resolvers for web frameworks shipped with QF-Test as a basis. The following procedure call shows an example of how to enhance the resolver for the Angular Material framework. Additionally to the preconfigured mappings for the Angular Material framework it maps all GUI elements with the…
Version 7.1.3 49.1.9Example for "CarConfigurator Web" demo As this approach is quite difficult to understand just by reading, we describe a sample implementation using the "CarConfigurator Web" demo in this section. You can find the "CarConfigurator Web" test suite at qftest-7.1.3/demo/carconfigWeb/carconfigWeb_en.qft. Figure 49.8: CarConfigurator Web As stated in the previous section we need to…
Version 7.1.3 49.1.6'CustomWebResolver' – Lists In order to resolve List components correctly, it is necessary to map the component containing all list entries, i.e. the list itself, as well as the components which represent the individual list entries. Class Required components and sub-items List Represents the List component, contains all list entries. Item:ListItem Represents the individual…
Version 7.1.3 49.1.1General configuration The 'Install CustomWebResolver' node offers the following functionality: Mapping of HTML objects to functional components You can map functional GUI objects as buttons, text fiels, data tables etc. to QF-Test components of a certain generic class. Advantages: - recording of additional criteria for recognition, - class specific checks, - indexing of…
Version 7.1.3 49.1.3'CustomWebResolver' – Tables In order to resolve Table components correctly, it is necessary to map the component containing all entries, i.e. the table itself as well as the components which represent the individual rows of a table and the individual table cell entries. Furthermore, the row containing all headings as well as the specific headings need to be mapped to generic…
Version 7.1.3 49.1.8'CustomWebResolver' – TabPanel and Accordion In order to resolve tab panels or accordions correctly, it is necessary to map the component containing all entries, i.e. the tab panel itself as well as the components which represent the individual tab panel entries. Class Required components and sub-items TabPanel Represents the tab panel component, contains all tabs.…
Version 7.1.3 49.1.5'CustomWebResolver' – TreeTable Tree tables are a combination of table and tree. For them, you map TreeTable the same way you would a normal table. Additionally, you need to map the open/close buttons of the tree nodes. QF-Test assumes that the tree components are located in the first table column. You can adjust this behavior with the configuration category "treetableResolver"…
Version 7.1.4 39.11Runtime only Some options of a more technical nature are not available via the user interface, especially if they are useful only in very specific cases and will do more harm than good in general. As mentioned in the introduction to this chapter, options can be set in 'Server script' or 'SUT script' nodes via rc.setOption(Options.<OPTION_NAME>, <value>) (see section 48.5 for…
Version 7.1.4 7.0+39.4SmartID und qfs:label The following settings define details for capture and replay of SmartIDs and qfs:label* variants. Please see section 5.6 and subsection 5.4.4.1 for details. Figure 39.30: SmartID und qfs:label-Optionen 6.0+SmartID recording (System) Server (automatically forwarded to SUT) script name: OPT_RECORD_SMARTID If this option is active, SmartIDs will be…
Nous utilisons des cookies "Matomo" pour l'évaluation anonyme de votre visite à note page web. Pour cela nous avons besoin de votre consentement qui est valable pour douze mois. La révocation est possbile n'importe quand sur notre page "Protection de données".
Configuration de cookies
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.
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 any page or sub-page.
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. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
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.