My images are identical, why do my image checks fail?

With multiple opened browser windows, how can I ensure that the correct is used?

This is how it starts every night. I barely have a moment of rest until I'm clicked and checked again. But it's fun, I'm the website www.qfs.de!

Here is the second article on how we test our website. We implement dependencies.

In case QF-Test is unable to identify the corresponding component in the application a ComponentNotFoundException get's 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.qfs.de!

This will be a blog series on how we test our new web site.

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.

After starting QF-Test a message is shown that Apple cannot check QF-Test for malicious software.

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.

In this article I explain how to prepare an Eclipse or standalone Liclipse IDE to connect to the Jython interpreter of QF-Test and allow enhanced debugging.

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.