QF-Test Reviews

1. I have been using QF-Test for 17 years, since 2005, for both Web and Java Swing apps. Very enjoyable to work with, especially if you are a creative individual. It gives me a deep sense of satisfaction.

2. Semi-automated development, very easy to create a framework. Test automation scripts should not be as complicated as API apps they test. It allows one to develop and try any number of alternative solutions for a problem within a very short time. Even at runtime, while at a breakpoint, you can create, redesign entire test cases, record and insert any additional functions. You jump back and force, change values of variables, test and retest new and old functions as many times as needed without stopping the program.

3. Graphical/image-based editor as opposed to hard coding, thus ease of comprehension even for outsiders. One manual tester automated a complicated scenario just by looking at my “scripts.” By the end of the day, you feel as fresh as in the morning.

4. Simple to use but provides broad functionalities for all possible scenarios.

5. Robust and flexible image verification in the GUI. You can record an image even in the cell of a grid. Nine different algorithm types allow making recorded images immune to variations in color and don’t update them for years, if ever.

6. Multiple steps in component/element recognition. Sometimes I ask developers to set a name or any other ID to guarantee uniqueness and minimize updates due to changes in API, but only to minimize updates if they add one more component to 10 similar ones.

7. Customer/tech support is exemplary. I am in New York and they are in Germany; nevertheless, usually, I get an answer the same or the next day. Even in an environment of high-security level like in my company, they have a lot of means to get all needed info and troubleshoot your issues.

There is nothing to dislike. The team listens to their customers. They added a few features upon my request. One or two of my requests they rejected because they thought about all their customers and whether the new addition would benefit the larger group. And I totally agree with this policy.

1. Allows keeping the number of automation engineers and functional/manual testers to a minimum. One engineer can develop, support, and execute thousands of test cases. Coupled with reasonable pricing, it’s very cost-effective. Once, management requested that I automate 400 test cases within a year to decrease pressure from manual/functional testers at release time because they were overwhelmed with the workload. It was challenging, but I did it.

2. Excellent, very detailed manual, plenty of tutorials and examples allow mastering the tool very quickly. If someone has already created a framework, new engineers pick up very quickly, even without prior experience with QF-Test.

3. Requires minimal input from app developers, if at all.

Seit 2011 arbeite ich bereits mit QF-Test in unterschiedlichen Projekten. Am besten gefällt mir die Gesamtstabilität, die unendlichen Möglichkeiten und natürlich der legendäre Support. Mit QF-Test kann man jegliche Projektherausforderungen schnell und einfach meistern.

Ich habe keine negativen Erfahrungen mit dem Tool gemacht.

Test it!

Komplexe Teststrategien lassen sich genau so einfach umsetzen, wie auch triviale einfache schnelle Testfälle. Mit QF-Test ist man immer am Puls des Projekts. Die Schnelligkeit des Tools fasziniert mich immer wieder.

The maturity and flexibility of the tool and the team behind, to solve customers changing requirement in UI testing.

Hard to say, as we do not actually use it ourselves intensively. We saw just saw it working (see below).

We are vendor of a product called Webswing which is a web server that allows to run any Java Swing application inside a web browser, using only pure HTML5.

We've been contacted by QFS to see whether their UI test tool QF-Test may also work for this special Java / Web system.

This cooperation worked out pretty well and QF-Test turned out to be a great tool even for such very special cases.

In fact the guys found a really cool way to allow UI tests previously developed for the Java application to be executed on a Webswing server via the web browser nearly unchanged.

Awesome!

By implementing the support for Webswing, QFS were able to help an important customer to reuse his extensive Java test base for his new web environment and so saved a huge amount of time and money.

Pricing is just right:

Many test automation tools are free, but these require significant effort to construct a 'framework' that handles component recognition, reporting, abstraction, re-use, CLI etc... additionally these free tools require costly maintenance when running against a shifting codebase of an application under test (AUT).

Conversely, "enterprise" testing tools which include a framework are frequently priced at an extraordinary rate.

QF-Test hits the 'sweet spot' between these two extremes by providing a low priced rich feature set inside a framework with an easy to create and maintain abstracted object map for your AUT.

Support is amazing:

I've been using the tool across dozens of customers with many specific problems that need to be solved. QFS (QF-Test vendors) typically respond with solutions to any issues within 12 hours, and continue to follow-up if needed. They don't close the ticket until the issue is truly addressed.

Technologies supported is wide:

Originating with Java Swing, SWT & JavaFX on Windows, Linux and Mac, then expanding by using the same consistent approach for handling web application testing.

Feature set is huge:

QF-Test is extensible with Jython, Javascript and Groovy, and supports everything that tools like Selenium do, but with abstraction built in. Saying that, in my experience 95% of test automation problems are typically solved using the "off-the-shelf" features shipped with QF-Test.

Shallow learning curve:

The tool ships with an array of examples that exercise built in applications under test. These examples have patterns that are re-useable and can be built on for the tester to use on their AUT with ease. Delving into these patterns is a simple activity with a high return on investment in upskilling. Additionally the manual, tutorial and context sensitive (right click) help allow quick understanding on how to use the tool.

The test artefacts are stored as *.xml files on a file system. Committing these to source control is sometimes problematic when handling diffs (e.g. merging branches in Git). It's a surmountable issue (split the tests into many smaller files for instance), but with monolithic test files, source control can be confronting to non-technical testers.

Download the trial version off the shelf at qfs.de and give it a go.

I work in agile development teams as a test automation developer running tests authored with QF-Test in various CI/CD pipelines against all sorts of applications (Swing, Web, RESTful API's).

With the tests triggered in pipelines, the necessity to have them running "green" within an iteration with coverage to exercise new changes in the AUT mandates a low maintenance cost. QF-Test allows this to happen.

QF-Test is a powerful tool for automated testing of Java, Web, dot net and now also native Windows applications.

It runs as Java application under UNIX / Linux, macOS and Windows.

QF-Test offers, like most GUI test tools, the possibility to record tests via Capture & Replay and to replay these tests.

QF-Test works with its own driver for the (re)recognition of GUI elements, but is also able to use the Selenium driver.

But QF-Tests offers much more than that.

With the possibility to implement your own scripts (in Jython or groovy), there is nothing to stop you from mastering (almost) any challenge.

QF-Tests own test suites (test scripts) are xml based and easy to handle after a flat learning curve. The xml-scripts are divided into three parts.

In the lower, actually the most important part, the user interface elements of the application under test are mapped to named objects that are easy to address.

These can then be used in procedures and functions (or even in self-written Jython / Groovy scripts), object attributes can be tested and addressed.

In the uppermost part of the test-suites, the test flows are mapped in a structured way using test case sets, test cases / test calls and test steps.

Due to the possibility of using variables in the procedures and functions, even in the mapping level, a data-driven GUI test can be mapped very easily via data tables, for example.

I have been using QFTest in my freelance work for many years in a wide variety of projects and for a wide range of requirements.

So far there has not been a challenge that could not be solved (at the latest with the help of the very fast and helpful support team).

I can't think of anything about this at the moment...

Give QF-Test a chance, it is easy to use..

The possibility to adapt the recognition of surface elements to customer specific conditions (Resolver and co.)

It's easy to learn in-self study and with the help of videos or webinars. The component recognition is very good. With a little practice the component recognition can be adapted individually to your needs or be optimized.

The look of the tool is a little out-of-date.

I was once struggling with the automation of reading and clicking on a special button on a PDF-File. But the support was very competent and could help me solve the problem with image-recognition.

We use the tool mainly to automate web testing. It's easy to reuse components and to become aquainted with an already existing project. This means every employee, knowing QF-Test, is able to understand every test automation project realized with QF-Test very easily.

The easy integration into Jenkins helps us to shorten the test cycles and to run tests during the night or on the weekend.

In general, the manual and the good support are a very important argument for QF-Test. The manufacturer QFS pays great attention to a constantly updated manual. This ensures that the information is helpful and that the manual is often used as a reference in everyday work. If the manual does not help, then I have always received helpful advice from QFS support.

The concept of using variables is very powerful, but not intuitive.

The chapter on variables is mandatory reading for all Tecnical Test Analysts who are supposed to write scripts that are to be used more than once.

In customer's project I had to test a web application in which the GUI elements are assigned the IDs dynamically. As a test manager I was unable to dissuade the external web developer.

Here it helped me that QF-Test allows variables in the parameterization of the GUI objects that are evaluated at runtime. In this way, the test automation could write the currently valid IDs in variables in a catalog of the web application and ensure the recognition of the GUI objects.

The best is to implemet GUI tests very easily in first step.

Some of error messages are not clear and are coufusing and I can't fine real root cause of the errors.

GUI interactive performance issues. Our purpose is to detect issues before our customers find them.