Running multiple tests at once could improve test execution time a lot (if raw system performance is not a bottleneck) while saving lots of infrastructure overhead because everything can run on one machine.
Sure, a team of testers can handle extensive test projects faster and better than a single person. But some things that may seem simple at first actually can become much more difficult when working in a team.
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.
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.