Blog

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.

Now it’s time! Now I can introduce myself to the world. Here I am! Can you see me? Hi! I’m the new website, www.qftest.com!

A very good solution of the combination of web technology and desktop applications is Electron. Almost every user knows or uses Electron apps. Popular apps like Skype, Microsoft Visual Studio Code or Discord are built using the Electron framework.

Packet soup or baking mixture, cook by yourself or bake? Concerning food opinions divide. Pros and cons. QF-Test doesn’t ship convenience food, you have to cook it yourself. But you will be given a variety of spices that will ease your life: the standard library qfs.qft. From a collection of fine salt and pepper to complex pizza spices, the genuine for every meal.

In their recent version of macOS, named “Catalina” (10.15), Apple introduced a feature protecting users from executing malicious software downloaded from the Internet. To separate “good” from “bad” software, Apple implemented a so called “notarization” process, and software which has not been “notarized” cannot be executed on macOS Catalina without further ado.

By the usage of script nodes QF-Test allows embedding of special custom functionality into your test cases. Typically, these scripts are supposed to be short and relatively simple containing just dedicated functionality, whereas the majority of test logic is done via QF-Test visual nodes.

OK, this is a really special case, but with the increasing use of the QF-Test license server this case is happening more often. The license server just has to be reachable by all QF-Test instances, which use a compatible client license for the server license. When starting, they ask explicitly just this license server if the requested license is still available.

You are interested in QF-Test, you already have a trial version and/or want to know more about this company? Most of the time you can only catch a superficial glimpse of the companies on their websites. How the employees are and what it’s like to work in this company is not really known. You may find an article or an award. Fantastic. But what is behind this appearance? I spent three weeks at QFS as an intern and would like to give you a little insight into the company behind the product.

If you want to use data from an MS Excel file in your QF-Test tests or want to write test results to MS Excel files then go on reading.

This is a short article about why QF-Test records geometry information for components, what impact these values have and how to change them either after or during recording.

Comme nous avons également étudié et que nous souhaitons aider les étudiants à rédiger leur thèse sur les tests de logiciels, nous avons décidé de créer une liste de référence pour les sujets pertinents relatifs aux tests.

Les systèmes d’intégration continue (CI-Systems) soutiennent les équipes dans leur travail constant sur les différentes sous-étapes du processus de développement logiciel.  L’objectif principal étant l’amélioration de la qualité des logiciels.

There‘s no way around using variables if a test suite has to to be flexible, reusable, and elegant. But where are variables set? Which value of the variable is used if I defined multiple ones at different positions? And how can I find out? This article aims to answer these questions.

If you are working with QF-Test scripting nodes, no matter whether you prefer Jython, Groovy or JavaScript, you will come across the QF module sooner or later. This module, accessible in all script nodes and script terminals via the variable qf, holds a bunch of helper methods designed to make the life of a script programmer easier.

You are working with QF-Test and something doesn’t work as expected? Then you can (as usually) search the Internet or do research at StackOverflow… A faster way is going on our channels …

Some days ago I had the pleasure to visit a Meetup Venue here in Leipzig, Germany. The topic was very interesting - “Experience with the introduction of Test Automation”. Many of the participants consider Web UI testing very fragile and cumbersome to keep in “Tests OK” status that’s why I I decided to write this series with the topic: No coordinates based Events and no Image based checks! QF-Test is smarter than that!

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.

QF-Test uses semi-hard events as default (based on web framework, browser and browser version, OS etc), but not all cases. There are three event types available.

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