Test suite tree: tree structure with test suite, procedures, component definitions, detail view on the right
Example use case: Day 1 on the project
You have recorded your first tests and want to structure them. Here you can see how even a grown suite stays clear and organized – test cases, reusable procedures and component information in one place, without file chaos.
QF-Test welcome screen
Links to demo video, quickstart, tutorial, manual, FAQ, demo suites, e.g. for the first start after installation – no empty interface, no guesswork. The welcome screen takes you straight to the right entry point, whether you prefer to watch a video or get started right away.
UI inspector with example suite: record/replay, low-code editor, tree structure of the recording
From everyday testing
You are testing a new web interface and want to quickly check whether a form works correctly. Not a single line of code required: start recording, perform your clicks, done. The result is immediately editable – not just a complicated script.
Emulator/test suite structure: test sets, test cases, procedures, component information, detail view
In practice: three months into the project
The team has grown, and so has the suite. A new colleague wants to adapt an existing test case. The tree structure immediately shows where test logic ends and reusable building blocks begin – no need to dig into unfamiliar code.
Test debugger: step-by-step execution, breakpoints, variable values
Typical use case
A test fails sporadically – but only on the CI server. With the integrated debugger you run the test step by step, inspect variable values at runtime and find the cause before the next meeting starts.
Run log with error: test run log as a tree structure, error messages, detailed information
Practical example
After the nightly test run, the run log shows: 3 of 47 tests failed. Instead of searching through log files, you expand the affected branches – the error message, a screenshot at the moment of failure and the exact step are immediately visible.
HTML report: overview of successful/failed/skipped tests, duration, error messages, screenshots
Use case: sprint review in just an hour
The product owner wants to know whether the new feature runs reliably. You send the HTML report – no QF-Test needed to open it, no explanation needed. Green is green.
Also available in dark mode
The QF-Test welcome screen
It contains a number of helpful links to the main entry points such as demo video, quickstart wizard, tutorial, manual, FAQ and demo suites.
Creation of automated tests without programming in dark mode
You can quickly create and replay your first tests via record/replay – no programming skills required. The recordings are fully editable in our low-code editor and you can add to and modify them at any point. The test run is presented in a clear tree structure.
Stable UI testing in dark mode
QF-Test reliably recognizes even complex elements such as dynamic trees and tables. The tests are tolerant to changes in the graphical user interface. This results in low maintenance effort and high reusability of the tests, the most important factor in software test automation. Thanks to the new SmartIDs, objects such as buttons or text fields are addressed even more directly, and it becomes possible to write tests before the application under test is fully developed (test-driven development).
Test debugger in dark mode
The integrated test debugger proves very useful for step-by-step test execution. It also allows setting breakpoints, continuing a test run at a different position, inspecting variable values, etc.
Run log with error
All detailed information and results of a test run are stored in the run log. Also presented as a tree structure, it allows easy handling and is the central resource for error analysis.
Interested in QF-Test?
Tell us about your project, and we’ll personally show you how QF-Test can support you.