of the standard library
qfs.qft offers the following functionality:
||Figure 45.1: Reduction of complexity for WebCarConfigurator demo|
nameto identify a component and saves them in the 'Name' attribute of the 'Component' node. You can configure
installCustomWebResolverto use a different HTML attribute as id.
You can use the following HTML features to identiy a GUI object:
The mapping of the HTML attributes can be subject to certain conditions. QF-Test offers the following options to set conditions for single mappings. It is possible to combine them.
A functional component often may consist of nested layers of elements. Some of the layers may have attributes useful for component recognition, others not. For recording and replay it does not matter which layer you map. The main thing is to has attributes for component recognition. QF-Test will also check nested components for further attributes and save them with the mapped QF-Test component. Example: Mapping of TabPanels and Accordions
In addition you get functional components such as combo boxes, lists, tables and trees which have to be implemented in HTML via several objects, named 'complex components' in QF-Test, i.e. a list, where you need to tell QF-Test which HTML object will be the list container and which HTML objects will be the list items.
The following sections provide a list of mandatory and optional GUI elements which need to be mapped for a complex component to be recognized as such, each containing a comprehensive example.
In most cases the HTML attribute
significant for component recognition and provides information about
the functional type of the component, sometimes it is other attributes.
For adapting QF-Test to those frameworks you need to implement
other resolvers additionally to
In this chapter, the focus is on the first two.
please get in touch with our support.
|Last update: 12/12/2019
Copyright © 1999-2019 Quality First Software GmbH