51.1.9.4 Next steps

As shown in the previous sections our first task for testing web-projects is to figure out how QF-Test recognizes the components and to create a corresponding dictionary. This task looks rather difficult at the first glance, but its result will drastically reduce the maintenance work due to component changes or hierarchy changes in later stages of your project. This is because QF-Test uses the relevant properties of your HTML components only, and not any information available.

chapter 61 shows a full list of all generic classes for standard components and complex components like lists or trees. We recommend that you map only those components which are really required and not every existing component. It's rather simple to extend the mechanism later.

Repeating the steps of the previous example we would now continue to map other components like menu items or tabs. As the mapping would be too much for this manual we provided a full sample in the demo test suite qftest-9.0.2/demo/carconfigWeb/carconfigWeb_en.qft in the procedure startStop.start in the last sequence, Install CustomWebResolver.

In order to use the created dictionary at every start of your web application you should move the Install CustomWebResolver node into your Setup node directly after launching the browser. In case you created the Setup node via the Quickstart Wizard, you will find the node in the sequence Install CustomWebResolver that can be configured accordingly.