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 49.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.
The following HTML code defines two tables, one as a data table and the other one for the layout of buttons:
|Example 49.13: HTML Table|
The following configuration for the 'Install CustomWebResolver' node only maps the data table to a QF-Test table component.
|Example 49.14: HTML table|
In the mapping of
the class type
myTablePanel was freely "invented"
to distinguish the
DIV element containing the data table
This allows us to use
in the mapping of the table.
The mapping for the column title
reads as follows: The attribute
type with the value
will be mapped to the generic class
TableHeader only if
the HTML tag name is
To make sure the mappings will only affect HTML elements with the
TD that are part of
a data table we add
ancestor: to each.
We do not want to record HTML elements with the HTML tag
that are not mapped to a QF-Test Table component.
Therefore, we add
in the category
ignoreTags in addition to the default entries
<SPAN> which, in turn,
make sure that unmapped
will not be recorded.
|Last update: 5/31/2023|
Copyright © 1999-2023 Quality First Software GmbH