In the last days, a vulnerability in the popular open source library log4j has been reported, nick-named Log4shell. QF-Test is not (and has not) been vulnerable to this attack, for a number of reasons.
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.
"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.
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.
We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months. A revocation, so-called opt-out, is possible at any time on our privacy page.