Question 1. What Is Qf-test?
QF-Test is a professional tool for the creation, execution and management of automated system and load tests for Java and Web applications with a graphical user interface (GUI). QF-Test has been developed and distributed by Quality First Software GmbH (QFS) since 2001.
Question 2. What Gui Technologies Are Supported For Testing?
For Java based applications the full toolkit set is covered starting with the traditional Swing (including Applets, Web start, ULC, CaptainCasa), its successor JavaFX and also SWT, the Standard Widget Toolkit from Eclipse, including Plugins and RCP (Rich Client Platform) applications. Furthermore QF-Test provides cross-browser testing of Web GUIs including HTML5, AJAX (Angular, Smart (GWT), GXT / ExtGWT, ExtJS, ICEfaces, jQuery UI, jQuery EasyUI, Kendo UI, PrimeFaces, Qooxdoo, RAP, RichFaces, Vaadin, ZK). Further toolkits can be integrated with little effort if required, e.g. SAP UI5, Siebel Open UI and Salesforce. PDF documents can also be tested by QF-Test.
Question 3. What Are Qf-test’s Outstanding Features?
Easy to use:
- Quick creation of tests with capture and replay.
- Excellent usability through QF-Test’s intuitive GUI.
- Simple composition of complex, high coverage tests without the need to program.
- Automatic adaptation to changes in the application under test.
- Intelligent recording and filtering.
- Full access to recorded sequences.
- Support for trees, tables and other widgets, even with dynamic content.
- Powerful algorithms for component recognition.
- Advanced programming elements if desired, like loop constructs, ‘try/catch’, dependencies and logical ‘if/else’ control structures as well as variables and procedures allowing modularization.
- Text processing with regular expressions.
- Full access to the Java API of the application under test.
- XML/HTML based test reporting, incl. screenshots.
- An extensive manual (over 1,000 pages) containing a user’s guide with many examples and a reference section.
- Tutorial for a quick start, with many easy to understand test scenarios.
- FAQ for basic questions – right here :).
- Both English and German language documentation.
- Example test-suites.
Question 4. Which Platforms Is Qf-test Available On (system Requirements)?
QF-Test supports Java version 7, 8 and 9 on:
- Windows (Windows 10, Windows 8.1, Windows 8, Windows 7, Server 2016, 2012, 2008 R2)
- Linux. Swing and JavaFX testing is also being used in other UNIX systems (Solaris, AIX, HP-UX…).
- macOS (except for SWT).
Further information – also regarding JDK-/SWT-/Browser-versions – can be found in the installation chapter of the Manual.
Question 5. How About Integration With Other Tools?
As QF-Test provides multiple interfaces (batch and daemon mode, scripting, …) and uses XML as primary data format a flexible combination and communication with other tools is possible (among others Quality Center, load testing tools like Noeload, Scapa TPP):
- Continuous integration and build tools (Ant, bamboo, Maven, Cruise Control, Hudson, Jenkins, …)
- Version management (CVS, SVN, Subversion, Clearcase, Git, Mercurial …)
- Issue and defect tracking (Bugzilla, JIRA, Clear Quest, Test Track Pro, Mantis …)
Special out-of-the-box integrations are available for the following test management products:
- ALM – Quality Center from HP
- Test Bench from Imbus
- QMetry from QMetry
- SQS-TEST/Professional from SQS
- Klaros from verit
- Test Link, Open Source Solution
Question 6. We Are Testing Our Website Already With Selenium. Do I Need Qf-test Then?
- With Selenium developers can quickly create web-tests. However, if tests get more complicated or should be easily maintainable, and when also non-developers are part of the testing team, we recommend switching to QF-Test. To control modern browsers, QF-Test uses, like Selenium the Web Driver-standard. It is also possible integrate existing Junit-based Selenium tests via Unit test steps or via the Selenium API in scripts directly in visual test procedures.
- The tool price of QF-Test in comparison to Selenium is just a small part of the test project costs. The main factor is manpower. So the effectivity of implementing and maintaining tests is playing a decisive role. And QF-Test already has maintenance, support, further development, bug fixes etc. included.
Question 7. I Run Unit Tests, Why Is That Not Sufficient?
Though indispensable, unit tests can only test small parts of a system in isolation (steering-wheel OK, motor OK). GUI based testing exercises an application as a whole (steering-wheel and motor taken together don’t guarantee roadworthiness).
Question 8. What Is The Use Of Test Automation?
Automated software testing reduces time and costs spent on quality assurance. Comprehensive automated tests, executed regularly during software development, will detect bugs at an early stage. The reproducible security thus achieved ensures higher quality and shorter time to market at lower maintenance expense. A tool with reliable component recognition and low maintenance effort is a precondition, however…. and a few other conditions (tester, test design…).
Question 9. What Can I Tell My Boss Who Doesn’t Want To Spend Money?
Thanks to the low price for licenses and the good usability of QF-Test you can start quickly with efficient testing and have a high return on investment (blog). Just compare the costs for licenses with common costs for developers’ or testers’ wages and the costs of bugs detected after release – not to mention the damage to your company’s reputation. See Benefits for decision-makers.
Question 10. Is A Trial Version Available For Download?
Yes. You can download the trial version here.
Question 11. Which Gui Technology/technologies Do I Need To Buy?
QF-Test licenses can be purchased specifically for the GUI technologies actually needed. In order to determine the GUI technologies for your application, open your test-suite(s) and run all your client(s) via QF-Test. After having executed your tests, please open the ‘Clients’ menu. There you can see the GUI technologies used in  brackets. In the example there are two clients running using [Swing] and [Web]; all combinations out of [Swing], [Swt], [FX] and [Web] are possible.
Question 12. How Much Does Qf-test Cost?
License types and prices for QF-Test are listed on the page Prices.
Question 13. Does Qf-test Need An Additional License Server?
No, not necessarily. QF-Test handles multi user license management for local networks by itself, provided that IP multicast works. For floating licenses across multiples sites and in case of restricted networks, a license server is available.
Further general information can be found in the product description and technical details in the license server manual.
Question 14. Do Tests For The Graphical User Interface (gui) Make Sense For Me?
- If you don’t plan changing your graphical interface within the next period of time completely, GUI tests definitely make sense.
- The system as a whole is tested via the GUI and not the GUI itself. This is a common misunderstanding in GUI test automation. The GUI tests are executed from the end user’s perspective on a “living” system.
- You can reflect the whole workflow, how the end user sees and experiences the application.
Question 15. Which Kind Of Gui Tests Do I Want To Automate?
Functional tests to check whether the function is working or non-functional areas like load and performance of the software. Is it better for you to use one tool for both or is it even better to use two tools for these separated sections.
Automate tests of software with frequent code changing’s that you want to check regularly and that are boring for manual testing. As an exciting task testers then can focus on test architecture, test design and manual testing of advanced use cases. This can save time and money, but the initial costs of test automation must pay off of course.
Question 16. How Do I Select The Right Tool?
First of all create a list of criteria for tool selection (Exemplary check list of QF-Test)
On the one hand you surely have several “must have” criteria in mind like the supported technologies, platforms, integration in the build process or stable recognition of graphical elements of your software. On the other hand there are “nice to have” criteria that you would give up in favor of another aspect. You then can test, evaluate and compare the different tools regarding these criteria. Then you only have to choose one.
Another aspect is how you want to create the test: Do you want to code or record them via capture/replay; do you follow a keyword-driven or behavior-driven testing (BDT) approach.
Most importantly the test team should accept the tool.
LoadRunner Interview Questions
Adv Java Interview Questions
Adv Java Tutorial
Core Java Interview Questions
QTP Interview Questions
Core Java Tutorial
AJAX Interview Questions
LoadRunner Interview Questions
Selenium Interview Questions