Blog

In most cases we are dealing with more or less straight-forward UI components,such as buttons and text fields. Nevertheless we often have to deal with morecomplex UI components like trees, tables and lists too. These UI components have sub-items.

Sensitive information like passwords should be treated with care. However often tests need to fill out a login form and thus these tests require to know the password.

Via the run log QF-Test provides a detailed log about the actions it executed during a test run. The overall results of this run log can be summarized in other reports like the HTML/XML/Junit report.

Procedures (also called function or subroutine) may be used in order to solve often (re-)occurring challenges.

Even in early stages of development Capture & Replay offers a easy way to create tests. An early start of such regression tests and the assignment of unique names / IDs are the most important bases for efficient (due to stable recognition) test automation.

You want to purchase QF-Test licenses or are interested in training or consulting? This works unbureaucratically.

Sometimes it is necessary to perform mathematical calculations in QF-Test, e.g. in order to calculate the expected height of a UI element in dependence of the complete window size or the exact clicking position for a mouse click.

A high percentage of executed code indicates a little probability of undetected software bugs.

You want to try QF-Test and start now? You cannot save your tests created with the QF‑Test demo version? Then request a trial license.

Software bugs are annoying – for users and software manufacturers alike. The latter, however, should use bugs to continually improve the software, preferably from the beginning of development. Nevertheless, there will probably never really be flawless, right? Rather a philosophical question.

Our new QF-Test blog!