Quality First Software Articles by Quality First Software

Welcome to QF-Test

Meet QF-Test - our all-in-one platform for automated UI testing.

QF-Test
10.0

QF-Test Version 10.0

QF-Test 10 introduces powerful upgrades for WebAPI testing and AI-assisted validation.

QF-Test 10 introduces powerful enhancements for WebAPI testing.

Create end-to-end HTTP requests, manage authentication, cookies, and proxies through dedicated nodes, and customize workflows to combine UI and API automation in hybrid scenarios.

The new “Check Text with AI” node and the “ai” scripting module enable the integration of externally hosted LLMs to perform dynamic text validations and handle non-deterministic UI behavior.

Accessibility testing has also been significantly improved, with YAML-based configuration and additional checks for keyboard focus visibility and correct usage of the “lang” attribute.

Image-based testing is now much more flexible. Use the new “Set Image” and “Read Image” nodes to define image variables and apply them in the “Check Image” node and other image-related procedures.

There are many, many more features in QF-Test 10 to explore. You can find all the details in the Release Notes on our website.

Features for integrating the test management tools TMT and Xray as well as support for Oracle Forms are currently under development and will also be included in QF-Test 10 soon with upcoming minor updates.

QF-Test Version 10.0.1

2025-12-18

This maintenance release fixes startup issues under QF-Test 10.0.0 related to certain license files and addresses several other minor bugs.

QF-Test 10 – WebAPI, AI and more

Hi there! Today I’m going to show you how you can test web APIs with QF-Test 10. I’ll also walk you through the new AI features in QF-Test, and we have some exciting updates on accessibility testing for web applications in QF-Test 10.

Can I integrate web testing with QF-Test into my CI/CD Pipeline?

Yes, QF-Test can be integrated with…

… common CI/CD systems such as Jenkins and GitLab.

How can QF-Test be integrated into existing test strategies and workflows?

QF-Test can be easily integrated into existing test strategies because…

… it supports modular test structures and common approaches, such as data-driven or component-driven testing. With clear interfaces and reusable building blocks, the tool fits seamlessly into existing QA workflows. Existing test processes can thus be gradually automated.

What is web testing?

Web Testing refers to the systematic testing of web applications for functionality…

… stability, appearance, and behavior across different browsers and devices. The goal is a bug-free, user-friendly, and reliable user experience.

Which browsers and technologies are supported by QF-Test?

QF-Test covers all major browsers, including…

all major browsers Chrome, Firefox, Edge, and Safari, and is compatible with JavaScript frameworks such as Angular, React, and Vue. Additionally, the tool supports headless testing. You can find an overview at Web Testing.

Why should web testing be automated?

Automated testing saves time, reduces manual errors, and allows teams to efficiently support frequent releases.

For complex or dynamic web applications, automation is significantly more cost-effective in the long run than purely manual testing.

Can UI testing improve the usability of an application?

Yes. Usability tests show whether users can intuitively understand functions and complete tasks efficiently.

Findings from these tests help optimize user guidance, avoid misunderstandings, and increase overall satisfaction with the application.

How does UI testing contribute to accessibility?

Accessibility testing ensures that people with disabilities can also use the application to its full extent.

This includes screen reader support, correct alternative text, sufficient contrast, and full keyboard navigation. Accessibility testingis essential for both inclusion and compliance with legal requirements.

What is the difference between UI testing and GUI testing?

While UI testing covers all interactions on the user interface, GUI testing focuses exclusively on graphical elements such as buttons, icons, or menus.

In practice, however, the two terms are often used synonymously. It is crucial to clearly define which UI aspects are to be tested.

What is UI testing?

UI testing refers to the systematic testing of an application’s user interface.

This involves checking whether controls such as buttons, forms, or navigation elements are functioning correctly and whether user interactions are being processed as expected. The goal is to achieve an error-free, consistent, and user-friendly interface.

What methods are available for UI testing?

UI tests can be performed manually or automatically. QF-Test is a tool for automated UI testing.

Manual tests are suitable for initial evaluations of new features or exploratory testing, but they are time-consuming. Automated tests are ideal for recurring regression testing and enable frequent, consistent test runs—especially in agile development processes.

When should automated UI testing be used?

Automation is worthwhile…

… especially for frequently recurring test cases, such as regression tests before releases. It enables fast, reproducible results and reduces manual effort—especially in complex or extensive applications.

Why is UI testing so important?

The user interface is the most direct point of contact between users and software—problems have an immediate impact on the user experience.

Without UI testing, functional errors, unclear feedback, or defective elements often go undetected. Systematic testing increases quality, reduces support costs, and strengthens confidence in the application.

We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months.

Cookie Configuration

Functional cookies

We use functional cookies to ensure the basic functionality of the website.

Performance and statistics cookies

We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.

Cookie details
Description Vendor Lifetime Type Purpose
_pk_id Matomo 13 Months HTTP Contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
_pk_ref Matomo 6 Months HTTP Used to track from which website the anonymized user proceeded to our website.
_pk_ses Matomo 1 Day HTTP The Matomo session cookie is used to track the visitor's page requests during the session.
_pk_testcookie Matomo Session HTTP Used to check whether the visitor's browser supports cookies.
_pk_cvar Matomo 30 Minutes HTTP Temporarily store data about the visit.
_pk_hsr Matomo 30 Minutes HTTP Temporarily store data about the visit.