| Version 3.4.7 |
| Quickstart |
This chapter provides instructions on how to quickly set up your application as the SUT (System Under Test).
With the Quickstart Wizard QF-Test offers a convenient utility for creating a startup sequence for your application.
|
| ![]() |
||
|
| Figure 3.1: Quickstart Wizard | ||
You can open the Quickstart Wizard via the »Extras«-»Quickstart Wizard...« menu item. It will guide you step by step through the creation procedure and should be self explanatory.
As result the Wizard delivers a startup sequence under the "Extras", as shown in the following figure:
|
| ![]() |
||
|
| Figure 3.2: Startup sequence created by the Quickstart Wizard | ||
The setup sequence contains a start node that may vary in type and attributes dependent on your application. The start node is followed by a "Wait for client" node that ensures QF-Test connects to your application during the startup procedure. (Details about the different start node types and attributes can be found in section 4.3.)
SWT For SWT based applications an additional procedure call node for SWT instrumentation is added.
Web The standard startup sequence for web includes some additional nodes for setting variables and initializing browser cache and cookie settings.
When executing the setup sequence your application should start up and the "Start
recording" button
in the QF-Test toolbar should become
activated which indicates that QF-Test is properly connected to the SUT.
Now you are able to record and replay your first test sequences as described in chapter 5. There is also a learning by doing tutorial available from the QF-Test help menu which guides you through all features of QF-Test.
In case you are facing an error message or the red "Start recording" button stays inactive, please proceed with the following paragraph.
Troubleshooting:
If the record button stays deactivated something probably went wrong with the instrumentation.
Swing For Swing applications you need to check the instrumentation of your JDK again. Most likely, your application uses its own JDK located somewhere inside its own directory structure. Therefore, your best course of action is to use the instrumentation dialog to search for a JDK there as explained in section 4.1.
SWT For an Eclipse/SWT application first make sure that you specified the
correct application directory. You may want to take a look at the run-log (see section 9.1) to see if any warnings or errors were logged during execution of
the 'Procedure' qfs.swt.instrument.setup.
| Last update: 04/23/2012 Copyright © 1999-2012 Quality First Software GmbH |