Manual
 

TopTable of contentsPrevious Chapter: 49.1.2 The 'Install CustomWebResolver' nodeNext Page: 49.1.4 'CustomWebResolver' – TreeNext Chapter: 49.1.4 'CustomWebResolver' – TreeChapter Overview: 49.1 Improving component recognition with a CustomWebResolverPDF versionQF-Test
Version 7.0.7
'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 classes.

ClassRequired components and sub-items
TableRepresents the Table component, contains all rows and cells.
TableRowRepresents a table row.
TableCellRepresents a table cell.
TableHeaderRepresents a row of the table headers.
TableHeaderCellRepresents a header cell.
 Optional sub-items
CheckBox:TableCellCheckBox(Optional) Represents a CheckBox in table cell.
Icon:TableCellIcon(Optional) Represents an Icon in a table cell.
CheckBox:TableCellHeaderCheckBox(Optional) Represents a CheckBox of a table header cell.
Icon:TableCellHeaderIcon(Optional) Represents an Icon of a table header cell.
Table 49.1:  Mapping of Tables

In addition 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: 

<div role="datatablecontainer">
    <table>
        <th type="header">
            <td class="datacell">Form</td>
            <td class="datacell">Color</td>
        </th>
        <tr>
            <td class="datacell">Square</td>
            <td>Red</td>
        </tr>
        <tr>
            <td class="datacell">Diamond</td>
            <td class="datacell">Blue</td>
        </tr>
    </table>
</div>
<table>
     <tr>
        <td>
            <div class="button">Save</div>
            <div class="button">Cancel</div>
        </td>
    </tr>
</table>
Example 49.13:  HTML Table

The following configuration for the 'Install CustomWebResolver' node only maps the data table to a QF-Test table component. 

genericClasses:
- Button: button
- TableCell:
    css: datacell
    ancestor: TableRow
- Panel:myTablePanel: role=datatablecontainer
- TableHeader:
    attribute: type
    attributeValue: header
    tag: th
- Table:
    tag: table
    ancestor:
        type: parent
        className: Panel:myTablePanel
- TableHeaderCell:
    tag: td
    ancestor: TableHeader
- TableRow:
    tag: tr
    ancestor: Table
ignoreTags:
- <DIV>
- <SPAN>
- <TABLE>
Example 49.14:  HTML table

In the mapping of Panel:myTablePanel, the class type myTablePanel was freely "invented" 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.

The mapping for the column title TableHeader reads as follows: The attribute type with the value header will be mapped to the generic class TableHeader only if the HTML tag name is TH.

To make sure the mappings will only affect HTML elements with the tags TR and 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 TABLE that are not mapped to a QF-Test Table component. Therefore, we add <TABLE> in the category ignoreTags in addition to the default entries <DIV> and <SPAN> which, in turn, make sure that unmapped DIV and SPAN elements will not be recorded.

TopTable of contentsPrevious Chapter: 49.1.2 The 'Install CustomWebResolver' nodeNext Page: 49.1.4 'CustomWebResolver' – TreeNext Chapter: 49.1.4 'CustomWebResolver' – TreeChapter Overview: 49.1 Improving component recognition with a CustomWebResolverPDF versionLast update: 10/11/2023
Copyright © 1999-2023 Quality First Software GmbH

We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months. A revocation, so-called opt-out, is possible at any time on our privacy page.

accept
configuration
Cookie configuration

1. Functional cookies

We use functional cookies to ensure the basic functionality of the website.

2. Performance and statistic cookies

We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.

Confirm selection

Cookie details