QF-Test natively supports testing websites with Chrome, Firefox, Edge, some others and even good old Internet Explorer. But there are plenty of other, lesser-known browsers that you might still want to run your tests with, such as Chromium, Brave, Iron, Vivaldi and Yandex.

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. (The following blog article explains how to insert a procedure call.)

On a popular demand we have created examples on how QF-Test can be integrated with JIRA. 

"Why do my automated GUI tests break?" that was the seminar question of a student. With this, he asked the central question for test automation. Because the success of this, as well as the daily work of QA, stands and falls with the recognition of the objects - or their failure/breakage of the tests.

First Online QF-Test Meetup with users from Switzerland and three QFS team members.

A testimonial by "Mr. QF-Test" who recently started to place a walking pad under his desk so that his work on QF-Test is now done walking and he is so happy with it that he even volunteered to write a blog about it.

This article shows how to perform automated audits by use of Lighthouse and QF-Test e.g., to measure performance or SEO behavior of your website.

QF-Test exists in German and English. You can switch the language in QF-Test. It is easy you just need to know how to change the language settings.

Loading a web page in the browser and working with it may produce various errors. To log those errors you may use the linked test-suite.