Version 7.1.4 30Usage of QF-Test in Docker Environments 30.1What is Docker? Docker is a free virtualization software that makes it very easy to install and run arbitrary applications on physical computers or in the cloud. Docker was originally developed for the Linux operating system. Docker is now also available for other platforms, including Microsoft Windows and macOS. The virtualization…
Version 7.1.4 5Components Though they often go unnoticed, at least until the first ComponentNotFoundException occurs, the 'Component' nodes are the heart of a test suite, since stable component recognition is the central challenge of a good GUI testing tool. QF-Test takes care of it most of the time, but some special situations require manual definitions or interventions. Thus it is important to…
Version 7.1.4 5.2'Component' nodes versus SmartID Regognition criteria can be linked to events in tests in two different ways. With the classic method, the criteria are stored as attributes of a 'Component' node (see 'Component' node). These are then referenced in the tests via their 'QF-Test component ID'. Alternatively, GUI elements can be addressed directly by the recognition criteria via…
Version 7.1.4 18Testing Java desktop applications in a browser with Webswing and JPro5.2+ Webswing and JPro are two highly interesting solutions that bring Swing and JavaFX desktop applications into a browser. The underlying technologies, concepts and goals differ significantly, but the challenge for QF-Test mainly boils down to the same thing: There are two SUT clients that need to be tested…
Version 7.1.4 7.0+27.5JUnit 5 Jupiter In chapter 12 we described how to integrate JUnit tests into a QF-Test test suite, which creates a common run log combining the results from the unit tests with those from the other QF-Test test cases. With the help of the Java annotation @QFTest.Test it is possible to go the opposite way and include QF-Test test suites into a Junit 5 test case, integrating…
Version 7.1.4 28Integration with Robot Framework (Preview) 6.0+Preview Though fully functional, the Robot Framework integration is still considered a preview feature because there are no pre-defined Robot Framework keyword libraries available for QF-Test yet so you have to create your own (which is quite easy, see below). 28.1Introduction Robot Framework is a very popular framework for test…
Version 7.1.4 12Unit Tests With Unit Tests, i.e. component tests, you can check the functional units. They explicitly test the functionality of single components. For this reason they are much less complex compared to integration and system tests. The 'Unit test' node executes Unit Tests via the JUnit framework as part of a QF-Test test run. The results are available in the run log as well as in…
Version 7.1.4 20Testing web services4.2+ From version 4.2 onwards QF-Test offers the possibility to test web services. Unlike the well known capture replay model here you must take care yourself to build the HTTP request and verify or validate the responses and/or the results. It is highly suggested to use the existing documentation of the web services you will test. For testing SOAP web services…
Version 7.1.4 B.9.5QF-Test version 4.3 B.9.5.1Version 4.3.2 - September 11, 2018 Bugs fixed: Raising windows on Linux systems now works more reliably. If an 'Server HTTP request' node for a POST request contains parameters encoded directly in the URL, QF-Test now keeps the URL unchanged instead of moving those parameters into the body. Web Deleting cookies after the browser window was opened now…
Version 7.1.4 B.9.4QF-Test version 4.4 B.9.4.1Version 4.4.2 - December 11, 2018 New features: Support was added for Eclipse/SWT version 4.10 alias "2018-12". ChromeDriver was updated to version 2.44 (still for Chrome up to version 71). Bugs fixed: The license check of QF-Test versions 4.4.0 and 4.4.1 might refuse a QF-Test 4.3 license even when that license had a valid maintenance plan. An SUT…