![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
Version 6.0.5 |
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 classes.
| |||||||||||||||||||||||||
Table 48.1: Mapping of Tables |
In case of TreeTables, simply replace Table with TreeTable.
Additionally to the following example you will find a detailed instruction for mapping a table in Mapping of complex components like data-tables.
Example:
The following HTML code defines two tables, one as a data table and the other one for the layout of buttons:
| ||||
Example 48.1: HTML Table |
Below parameters for installCustomWebResolver
only map the data table
to a QF-Test table component, however, not the HTML table used for the layout of the buttons.
| |||||||||||||||||||||||
The procedure call maps only the data table as a Table component. The table layouting the buttons is not to be recorded. The only way to distinguish the two is that the data table is in a container object with a role attribute.
Have a look at role=datatablecontainer=Panel:myTablePanel
. There,
we use our own class type myTablePanel
to distinguish the DIV
element containing the data table from other DIVs
.
This allows us to use @::parent=Panel:myTablePanel
in the mapping of the
table to make sure it is a data table.
The mapping for the column title type=header=TableHeader=TH
reads as follows: The attribute type
with the value header
will be mapped to the generic class TableHeader
only if
the HTML tag is th
.
To be sure the mappings will only affect GUI elements with the
tags TR
and TD
that are part of
a data table we will append @::ancestor=...
to each mapping.
We do not want to record GUI elements with the tag TABLE
not mapped to a QF-Test Table
component. Therefore, we will enter TABLE
in the parameter ignoreTags
, additionally to the standard entries
DIV
and SPAN
which, in turn, have the effect that
unmapped DIV
and SPAN
objects will not be recorded.
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | 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.