Version 8.0.1 |
Evaluation and licensing | |||||||||
| Is an evaluation version available for download? | ||||||||
Yes. Please visit www.qfs.de/en/qf-test/download.html. | |||||||||
| Do I need anything else? | ||||||||
Normally a license file is required to run QF-Test. It will run without a license, but it will not let you save any files or load any files that were not provided by Quality First Software GmbH. This is sufficient for getting a first impression, working through the tutorial and making a first attempt at running your application under QF-Test. To go beyond that, you'll need a license file. | |||||||||
| So how do I get a license? | ||||||||
You can obtain a free trial license valid for 4 weeks by filling in the request form at www.qfs.de/en/qf-test/free-trial.html. | |||||||||
| How much does QF-Test cost? | ||||||||
License types and prices for QF-Test are listed at www.qfs.de/en/qf-test/pricing.html. | |||||||||
| 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 dedicated license server is available. The license server itself is free of charge and server licenses are very reasonably priced. For further information about the license server, please get in touch with QFS via <sales@qfs.de>. | |||||||||
Support, training and feedback | |||||||||
| Where do I get help troubleshooting? | ||||||||
| |||||||||
| What about training for QF-Test? | ||||||||
QF-Test trainings for beginners and advanced users in German and English language take place regularly here at QFS. There is also the option for webinar-based or on-site consulting and training. Details can be found at www.qfs.de/en/qf-test-support/training-consulting.html. | |||||||||
| How can I request an enhancement to QF-Test? | ||||||||
Enhancement requests are welcome anytime at support@qfs.de. | |||||||||
| Where do I report a QF-Test bug? | ||||||||
Simply send an email to qftest-bug@qfs.de. and we will have a look. Please be sure to provide as much information as possible, especially test suites and run logs. | |||||||||
Test execution | |||||||||
| Why do tests fail today that were OK yesterday though nothing changed in the meantime? | ||||||||
As the first step, please ensure that really nothing has changed as automatic updates of Java or browser versions may happen without being recognized. Irrespective of changes there can be tests that fail only occasionally for no apparent reason. This may sound like a bug in QF-Test, but that's rarely the case. In complex, multi-threaded environments, many actions and interactions depend on timing. The first thing to try is to introduce delays at critical points. If that helps you can focus on minimizing the delay by using 'Check' nodes with a timeout or 'Wait for component to appear' nodes to wait for a certain condition. If delays don't help you need to dig deeper and try to understand what's happening. It's not unlikely that the root cause is a bug in your application - typically a tricky one that shows only occasionally depending on timing or other circumstances. The blatant, obvious bugs are typically found earlier - these tricky ones are part of what testing is all about. The detailed logs and screenshots that QF-Test creates help analyzing such situations. Our support can help you interpret the data and isolate the relevant information to forward to development. | |||||||||
| How do I run a test automatically from the command line, a test management tool or some other kind of script? | ||||||||
You can run QF-Test in batch mode through the command line argument
| |||||||||
| Is it possible to test two applications running at the same time in two different JVMs? | ||||||||
Yes, just start two SUT clients with different names. You can then control both of them. | |||||||||
| I've got a long-running test and QF-Test runs out of memory. How can I prevent that? | ||||||||
To increase the available memory, start QF-Test with the argument -J-Xmx1280m (or an even greater value; QF-Test uses up to 1024 MB by default). On Windows you can alternatively use the QF-Test Java Configuration tool, available from the Windows system menu. On Linux rerunning the QF-Test setup script (setup.sh) also lets you adapt memory usage. Of course the amount of memory you can use depends on your computer. Please refer also to chapter 1 for further details. There are a number of ways to reduce the memory use of QF-Test:
| |||||||||
|
Hard mouse events and drag'n'drop operations do not work flawlessly, components cannot be found,
the run log contains black or corrupt screenshots. What do I have to take care about for test execution? | ||||||||
GUI testing requires an unlocked, active desktop. That is the only way to ensure that the SUT behaves the same as if a normal user interacts with it. To make sure that your test environment complies with this requirement, you'll probably need to tweak its setup. This holds true notably for continuous integration and build tools like Jenkins (c.f. chapter 28). Otherwise you can run into serious trouble during Test execution, for example black screenshots in the run log (c.f. section 7.1), failing drag'n'drop operations, non-working hard mouse events or even problems during component recognition (c.f. chapter 5). Java WebStart applications fail to start up. Chapter Hints on setting up test systems contains useful tips and tricks to set-up your test systems. Before running a GUI test, check whether the following conditions are met:
Technical background: To get round all that problems you should consider to work with virtual machines, especially from a security point of view. If you execute the tests on a virtual machine, the above mentioned requirements apply for this virtual machine only, not for the host. You can lock the host and don't care about session management on the host. | |||||||||
Scripting | |||||||||
| How can I access objects in my application that are not components? | ||||||||
You cannot get an object out of the blue, some kind of registry must
exist that returns the object from a class static method. Typical
examples in the standard Java API are
| |||||||||
| Fine, but how do I use these from Jython, Groovy or JavaScript respectively? | ||||||||
This is standard Jython stuff: Simply import the class and call
its methods, e.g. | |||||||||
| How can I access additional Java classes from a script? | ||||||||
To make additional Java classes available to Jython, Groovy and JavaScript, put them in a jar file and place that in QF-Test's plugin directory (see section 49.2). | |||||||||
| How can I throw an exception from a script? | ||||||||
There are two ways to do that:
| |||||||||
| Which external editor should I use? | ||||||||
That's a matter of taste, to some even religion. A comprehensive list of editors for all kinds of operating systems that support Python syntax highlighting and other goodies is available at https://wiki.python.org/moin/PythonEditors. There are probably dozens of suitable editors with syntax highlighting for Jython, Groovy and JavaScript - jEdit (www.jedit.org) is only one of them. | |||||||||
Web | |||||||||
| How do I know which web UI toolkit is used for my web application and what do I do if it is not directly supported by QF-Test? | ||||||||
If possible, please ask your developers about UI toolkits or JavaScript components used. | |||||||||
| Why is this small file-upload/file-download dialog showing up before the real file selection dialog gets displayed? | ||||||||
Before a file selection dialog is displayed the QF-Test browser is showing up a small dialog with an OK-/Cancel-button. This helper dialog is needed by QF-Test to get the data out of the file selection dialog since this dialog is created natively by the operating system. After clicking the OK-button in the helper-dialog the native file selection dialog is displayed and you can enter the filename or select the file directly. | |||||||||
| Why does the replay of an already recorded file-upload-/file-download-sequence fail if I use another browser and how can I bypass that issue? | ||||||||
Depending on the implementation of the file-upload-/file-download on a specific page the
replay might get a bit complicated and even vary between different browsers. The QF-Test
standard library | |||||||||
| I get an error page notifying me about untrusted certificates. Unfortunately the standard dialog to add an exception is not working properly. How can I solve this problem? | ||||||||
This problem won't occur in QF-Test version 3.5.1 and higher, because SSL certificates are now accepted automatically. Please use the following workaround if you are using an older version of QF-Test. There are different approaches to add a certificate using firefox. Solution 1:
| |||||||||
| I'm getting an OutOfMemoryError for the browser. How to increase memory for the QF-Test browser? | ||||||||
In general it is recommended to create the setup sequence by use of the quickstart wizard. In the resulting sequence within the step "Start browser without window" there is a "Start browser" node in which you can specify the maximum memory as part of the Java VM parameters via e.g. -Xmx384m, which means 384 MB maximum memory. The current default is 256 MB.
| |||||||||
| The web-application opens a popup-window. If I try to close this window using a 'Window event' "WINDOW_CLOSING" the main-window is closed instead of the popup-window at times. How can I ensure that the correct browser-window is closed ? | ||||||||
In order to distinguish those windows QF-Test requires additional information. This information specifies which window should be used for replaying events. It has to be set at the 'Wait for document to load' node as well as for the recorded 'Web page' in the attribute 'Name of the browser window'. You can reach the recorded 'Web page' quite fast via right mouse click at the 'Wait for document to load' node and selecting »Locate component«.
We recommend to set that attribute to Specifying the attribute 'Name of the browser window' allows QF-Test to evaluate the content of that attribute in addition to the web page's URL for recognizing the web page itself and all underlying components. That's why QF-Test is able to distinguish between both windows during replay. Setting that value for the attribute at the 'Wait for document to load' node assigns a new name to that window from QF-Test's perspective. You can see that name in the titlebar of the browser as well.
Before replaying the respective 'Wait for document to load' and events for that popup window you need to set
the variable Now you can replay those events.
It is recommended to reset the variable
If you have already recorded some tests, you should update your test suite using a global replacement action for the
attribute 'Name of the browser window'. This action should set all values of that attribute from empty to You need to repeat that replacement action for any test suite which contains event and component nodes for that web page. |
Last update: 9/10/2024 Copyright © 1999-2024 Quality First Software GmbH |