Testing Windows Desktop applications
QF-Test masters complex elements like dynamic trees and tables. The tests are tolerant to UI changes. The sophisticated recognition mechanism leads to extraordinary maintainability and low maintenance effort the most important factor in software test automation. Objects like buttons or text fields are abstracted and recognized easily by generic components.
QF-Test offers flexible integration (primary via XML) with other formats and tools like Jenkins (with its own Plugin, watch Video), Docker/ Docker Container, Hudson, Maven, Ant, Bamboo, CruiseControl, TeamCity; CVS, Subversion, SVN, ClearCase, Git, Mercurial; JIRA, Bugzilla, ClearQuest, TestTrack Pro, Mantis. Test management interfaces to HP ALM - QualityCenter, Imbus TestBench, Klaros by Verit and the Open-Source solution Testlink. For further tools just ask us.
Detailed run-logs with debugger functionality in HTML and XML format for an effective error analysis including screenshots of the error situation. Automatic error handling, which grants continued execution of the whole test collecting errors in a single report. Verification points as standard checks or custom checks (via scripting).
Testing PDF documents can be tested like a normal application with textual and graphical checks for individual elements). There are also algorithms for blurred image comparisons.
We are perpetually developing:
|Java UI testing||All Java UI-technologies: Swing, JavaFX, AWT, SWT, Eclipse Plugins, RCP, WebStart, Applets, RIA, ULC, Captain Casa, JavaFX SubScene components, combinations of them (e.g. Swing with embedded JavaFX components). Custom technology example: adcubum SYRIUS.|
|Web UI testing||Static and dynamic UI components: HTML5, AJAX: QF-Test supports completely frameworks like Angular, React and Vue.js. Also extensions for dedicated UI toolkits are integrated in QF-Test, like Smart (GWT), ExtGWT, ExtJS, ICEfaces, jQuery UI, jQueryEasyUI, Kendo UI, PrimeFaces, Qooxdoo, RAP, RichFaces, Vaadin and ZK. Further toolkits can be integrated with little effort if required, e.g. SAP UI5, Siebel Open UI and Salesforce. Headless browser for Chrome and Firefox. Mobile emulation mode for web applications. Testing Electron applications.|
|Hybrid Systems||Embedded browser components can be fully accessed, especially JavaFX WebView, JXBrowser and SWT-Browser. Custom technology examples: GK Software, FirstSpirit. Testing Electron applications.|
|PDF documents||Testing PDF documents like a normal application (with textual and graphical checks for individual elements). Testing PDF documents Video|
|Test automation principle||Regression tests and Load tests : Record/replay for quick test creation, sequence control, clear graphic presentation of the test run in tree structure, layered architecture allowing a modularized presentation (reuses redundant test-“code” avoiding the the maintenance test trap), advanced scripting.|
|Component recognition, robustness of tests, timing synchronization||Masters complex elements like dynamic trees and tables by abstract generic components. Sophisticated recognition mechanism leads to extraordinary maintainability. Tests tolerant to UI changes. Tests should be as fast as possible, but not faster - otherwise the SUT will be overwhelmed and produce errors that are not.|
|Maintenance effort / reusability||Low effort and high degree of reusability due to stable component recognition and modular build.|
|Generic components||Recognition of technical components (buttons, test fields…) is optimally abstracted, helps to reuse tests over more technologies and to use common actions without the necessity of capturing every single field.|
|Data-driven testing||Data drivers allow for flexible integration of internal or external data, e.g. from CSV and Excel files, also direct database access. Other data sources can be integrated via script extension. Allowing a test case to be executed exhaustively with an array of data variants.|
|Basic procedures||Automatic creation for basic component access procedures, which is highly effective especially for form-based applications.|
|Error analysis||Detailed run-log, debugger functionality including breakpoints and analysis of variables.|
|Test case preparation||Dependency management for test preparation enables independently executable test cases, including automatic error handling.|
|Reporting||Configurable test documentation and reports can be created at the push of a button or via command line execution.|
|Test management||Pragmatic small scale solution included. Easy integration with third party solutions. Dedicated integrations are available for HP ALM – QualityCenter, Imbus TestBench, Qmetry, SQS-TEST/Professional, Klaros from Verit and the open source solution Testlink.|
|Continuous integration||QF-Test offers flexible integration with other software testing tools (Ant, Bamboo, Bugzilla, ClearCase, ClearQuest, CruiseControl, CVS, Git, Hudson, Jenkins, JIRA, Mantis, Maven, Mercurial, Quality Manager, load tests with NeoLoad and webinar video , Scapa TPP, Subversion, SVN, TestTrack Pro…). |
For Jenkins an additional Plugin is available which facilitates the integration, see Video.
|Test preparation||No additional preparation necessary: The quickstart wizard automatically instruments applications under test so that they're ready to be tested immediately. For test execution two screens are helpful.|
|Test scripts||Concise and comprehensible. Effortlessly extendable, can be modified even during debugging. Recurring actions can be modularized in procedures. Then they are parametrizable to reach a high degree of reusability. Furthermore this increases the maintainability enormously because necessary adaptions are just required in the procedures. Structuration of the tests in different test cases which can be merged into test case sets. Different test scenarios can be constructed, too.|
|Verification points||Direct recording of standard checks. Customized checks possible via scripting.|
|Image testing / comparison||Multiple algorithms also for fuzzy comparison. Convenient diff view for validation of deviations.|
|Object mapping||Component information is saved in a specific area of the test-suite during recording and can be edited anytime. Mechanism for automatic updates available.|
|Tests in batch mode||Extensive options for configuration via command line parameter for both Windows and Unix/Linux shells. Can be integrated into build environments without problems. Option to start additional steps after a test run through a return value.|
|Remote execution||Test can be executed also on a remote machine utilising a daemon.|
|Error handling||Automatic error handling, which grants continued execution of the whole test collecting errors in a single report.|
|Run-logs and reports||Detailed run-logs contain all information for an effective error analysis (incl. screen shots of application once an error occurs). Customisable summary reports in HTML and XML.|
|Test modification||Tests can be edited fully and modified at any place in the execution path. Test debugger offers valuable assistance.|
|Teamwork||Modular structure of tests and an import mechanism for the component information enable smooth teamwork.|
|Formats and version management||Both test-suites and run-logs are XML files and thus well-suited for version management.|
|Keyword driven testing / behavior driven testing||Keyword driven and behavior driven development (BDD) / testing allows the execution of test cases directly without having to create them in QF-Test. Text steps can be read in from a planning document or the specification, e.g. Excel or another test management tool and afterwards be executed.|