Dear QF-Test users and interested parties,
Wecome to another edition of our newsletter. Today we have some exciting highlights for you in the following topics:
1. QF-Test Major Release 6.0 with Android, SmartIDs and much more
2. New Articles and Videos
3. Better Together: User Groups for Talking About QF-Test
4. Next QF-Test Training Dates 2022
5. Release Notes for QF-Test Version 6.0
It's done. QF-Test 6.0 is finally ready for release.
The main headline is support for testing Android applications. The familiar features and concepts of QF-Test can be applied to creating tests for Android applications on virtual and real devices with ease and efficiency.
At least as relevant is the new concept of SmartIDs, which are an alternative way of addressing components. SmartIDs encapsulate relevant information directly in the component ID so that component nodes become optional. The idea is to keep simple things simple and use the full range of information in component nodes only for the tricky cases. This paradigm shift is still under development and deserves its own major release, but in response to the enthusiastic customer feedback on the existing functionality and stability we are making it available now in the form of a - fully supported - preview feature.
The SmartID concept has also paved the way for integration of QF-Test with Robot Framework, letting fans of Robot Framework implement their keywords via QF-Test procedures. The tool integration carried out with a pilot customer will be presented at the RoboCon conference (May 19-20, 2022).
Among the many other improvements, the following stand out: You can now run QF-Test itself with Java 17 for vastly improved display on scaled monitors, QF-Test reports have been revised with a more modern look, screenshots for the run-log are taken of relevant screens only and duration indicators assist in analyzing the time spent during tests. Major version updates like the switch to Groovy 4 or support for testing Java 19 become mere side-notes in the detailed release notes in section 5 below or online.
Since the last newsletter we have published more articles and videos about QF-Test and the world of software testing. Have a look:
This is a topic which has been on our minds for some time. Recently, a couple of customers got in touch with us asking for more in-depth exchange with other users of QF-Test – especially with those working with comparable applications and facing similar challenges.
Would you like to participate in some kind of user group? Get in touch at service@ and let us know the types of applications you're testing, for example ERP systems. qfs.de
After the last newsletter, a few interested people have already contacted us about the following topics:
-java <executable>). This provides crisp display on scaled monitors and enables support for plugins that require newer Java versions.
errorDelayin the procedure
qfs.utils.logMemoryin the standard library
qfs.qftare used to introduce a short delay in case the
errorLimitare exceeded, followed by an additional garbage collection and another check.
qfs.utils.xml.compareXMLFileshave been improved.
qfs.web.browser.settings.setDirectDownloadin the standard library
qfs.qftallows to download files directly into the directory provided, suppressing the download dialog. Currently for CDP-Driver connection mode only.
FrameNode.getFrameElement()was added to the pseudo-DOM API of QF-Test.
consoleOutputValuein the procedures
qfs.web.browser.settings.setTerminalLogsin the standard library
qfs.qftit is now possible to also set the type of the terminal logs.
The following features are not yet complete, but development has reached a point where they are already of great use and the released functionality can be relied upon without concerns about backwards compatibility.
SmartIDs enable a flexible, easy recognition of components directly from the 'QF-Test component ID' without recording component information first. Please see section 5.6 and 'Component' nodes versus SmartID for detailed information.
minisetup_admin.exe- can now be run in silent and very-silent mode, similar to the full installation.
qfs.autowin.acrobat.saveAsTextin the standard library
qfs.qftnow also works for Acrobat Reader version 22.1 and up.
rc.clearTestRunListeners()in a server script in batch mode broke the output resulting from the command line argument
uiautomodule directly in your scripts and reference class names directly, you may need to adapt the class names according to the supplied JavaDoc.