When companies start comparing good test automation tools for web tests, often the following question occur:
What is the difference between QF‑Test and the freeware Selenium? Which one fits to my team and our requirements best?
Instead of an either-or-question we recommend using the benefits of both tools. With Selenium (or the extension Selenium IDE) you can you can, for example, work when dialogues play a minor role in the system test. However, QF-Test is better suited for dialogues. Also you can only use Web tests with Selenium in Firefox (playback is also possible in several browsers). QF-Test further more supports additional browsers for web tests (Internet Explorer, Edge, Safari, Chrome... also 64bit) and is easier to handle for testers. You can even integrate your existing Java based Selenium tests in QF-Test and since QF-Test version 4.1 develop combined Selenium/QF-Test tests. Whenever bugs occur testers and developers can communicate quickly and have a common basis for the same target of a high quality software.
Usually a much more important question occurs shortly afterwards: Why should I pay for a commercial tool instead of using a freeware tool?
This question can be answered fastly...
Attila Enez, Tester, Hamburger Pensionsverwaltung, Hamburg, Germany:
After two mayor versions we abandoned Selenium due to this high maintenance effort.
Liviu-Aurelian Rau-Neascu, Senior Technical Analyst, Bucharest, Romania:
I find it is a shame that my technical peers never experienced the productivity gains we experienced using your product. Many have difficulties envisioning a painless Test Automation experience. They "know" that Test Automation is extremely hard and expensive since all they ever used were Selenium and other wrapper tools around Selenium that require some programming knowledge. Your product could be a game changer in so many organizations.
|Setup and configuration|
Easy installation, also for non-programmers
Combined / hybrid applications
|Target user group|
|Capture & Replay|
Recording of actions
Recording of checks
|Firefox plug-in, restricted|
Direct editing of recorded steps
Robust object identification
Central GUI object map
|GUI objects have to be managed on code level|
Generic GUI object classes
Easy direct item access e.g trees, tables
Use of XPath expressions
Automatic GUI object synchronization
|Support for dynamic ids/ AJAX|
Explicit support for several popular AJAX frameworks
|Test-run analysis and reporting|
|Modularization / reusability||Easy modularization and reusability|
Easy definition and integration of data sources
|IDE integration / headless testing|
Professional support from the authors
Training/ Consulting from the authors
Check it out for yourself: