![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
Version 6.0.5 |
In order to resolve Tree components correctly, it's necessary to map the component containing all entries i.e the tree itself as well as the components which represent the individual tree entires. Furthermore you need to map the toggler button, which opens and closes a tree node.
| |||||||||||||||||||
Table 48.2: Mapping of trees |
In case of TreeTables, simply replace Tree with TreeTable, i.e.
TreeTable
instead of Tree
,
TreeTableNode
instead of TreeNode
,
Expander:TreeTableNodeExpander
instead of Expander:TreeNodeExpander
etc.
Example:
The WebCarConfigurator demo
(qftest-6.0.5/demo/carconfigWeb/carconfigWeb_de.qft
)
contains a tree. Please open the specials dialog via the
menu »Options«-»Specials...«,
select a model and click the Button 'Details'.
When you have a look at the css classes recorded by QF-Test or analyse the web page with the developer tool of a browser (cf. subsection 48.1.2) you will find the following HTML structure (slightly simplifies and shortened):
| ||||
Example 48.2: HTML Tree |
In the CarConfigurator demo test-suite you will find the mapping for the tree
in the procedure call to qfs.web.ajax.installCustomWebResolver
.
It is located in the procedure startStop.start
in the last sequence,
Install CustomWebResolver
.
![]() | |||
Figure 48.5: WebCarConfigurator |
In the value field of the parameter 'genericClasses' the following entries map the tree:
| |||||||||||||||||
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | Last update: 3/15/2023 Copyright © 1999-2022 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.