Articles par 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.

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.

Large test projects may consist out of several thousands of test cases. Often executing them all would need a considerable amount of time, even if multiple machines are used in order to replay the different tests. The solution are tags.

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.

Les informations sensibles comme les mots de passe doivent être traitées avec précaution. Cependant, il arrive souvent que les tests doivent remplir un formulaire de connexion et qu’ils nécessitent donc de connaître le mot de passe.

Via le run log, QF-Test fournit un journal détaillé des actions exécutées pendant un test. Les résultats globaux de ce journal peuvent être résumés dans d”autres rapports comme le rapport HTML/XML/Junit.

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.

Un pourcentage élevé de code exécuté indique une faible probabilité de bogues logiciels non détectés.