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 47.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 47.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
we use our own class type
myTablePanel to distinguish the
element containing the data table from other
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
reads as follows: The attribute
type with the value
will be mapped to the generic class
TableHeader only if
the HTML tag is
To be sure the mappings will only affect GUI elements with the
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
in the parameter
ignoreTags, additionally to the standard entries
SPAN which, in turn, have the effect that
SPAN objects will not be recorded.
|Last update: 6/9/2022|
Copyright © 1999-2022 Quality First Software GmbH