Articles by Yann Spöri

For many people a picture is worth a thousand words. That’s why, in this article, we will show how to add various annotations to screenshots using QF-Test.

Today on first april we finally succeeded in a promising experiment for the automatic redesign of QF-Test – how useful the blockchain technology can be.

Excel files can be read into QF-Test using a simple procedure call where the procedure qfs.utils.files.readExcelFile must be called.

The TestRunListener interface can be used to execute additional actions before or after the execution of each node or in the case of any exception / error. This actions can (for example) be used for testdocumentation or error analysis. In the following some TestRunListeners are introduced (Jython server scripts).

It is relatively easy to take a screenshot of the complete picture with the help of QF-Test. For example, to create a screenshot of the current desktop, only the procedure logScreenshot must be called.

Especially when testing websites, you are now and then faced with the problem of having to parse JSON (=JavaScript Object Notation) strings. In this blog article, however, the JSON library provided by QF-Test should be described.

QF-Test it is possible to transform a node into another node type.

Since QF-Test 5.0.0 a new node was added, here you will learn how to use the comment node.

In case QF-Test is unable to identify the corresponding component in the application a ComponentNotFoundException gets thrown. Whenever an exception occurs QF-Test (by default) logs a screenshot.

In order to simplify test suite editing it is possible to assign colored marks to nodes. This feature is especially (but not only) helpful in the context of complex find and replace operations – in this case, the color markers can for example be used to indicate that a node still needs revision or that a node was edited successfully.

In some cases it is helpful to disable nodes temporarily. Here is a short article how to do this.

While testing an application, one of the most important steps is to verify that the actual state of the application is correct.

In most cases we are dealing with more or less straight-forward GUI components,such as buttons and text fields. Nevertheless we often have to deal with morecomplex GUI components like trees, tables and lists too. These GUI 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.

Sometimes it is necessary to perform mathematical calculations in QF-Test, e.g. in order to calculate the expected height of a GUI 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.