QF-Test

1. I have been using QF-Test for 17 years, since 2005. First for Java Swing apps and now for Web. 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 of 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.
8. 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.
9. 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.
10. Requires minimal input from app developers, if at all.

qf-test is the tool of choice for me because it is stable, fast and has endless possibilities. in addition, the support is legendary.

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! Be sure to check it out when you are looking for a UI testing tool.