|The Standard Library (Web)|
QF-Test provides a certain number of node types. If you need additional functionality you can implement it in a script node. To make life easier for you QF-Test comes with a set of procedures implementing the most commonly needed additional functions. You will find them in the standard procedures library.
When you cannot solve a problem using the provided node types it is a good idea to have a look in the standard library whether there is a solution to your problem. If you find a similar solution you can copy the procedure and adapt it to your needs. For information about scripting please refer the the manual, chapter 12 'Scripting'.
qfs.qft holds the standard procedures library.
As it is constantly being enhanced and distributed with every new version of
QF-Test you should not make any changes to procedures in that file, but
copy the procedure to your own test-suite if required and then adapt it.
To make use of
qfs.qft it needs to be included in your test-suite's root node.
With a newly created test-suite the file
qfs.qft is added automatically
to the list of included files.
qfs.qftis available within the table for "Include files".
qfs.qftto this list, if it's not already there.
A path information is not necessary for the
directory of QF-Test is contained in the library path (see also
Reference part of the manual).
qfs.qftstandard library. In the procedure chooser don't miss to switch to the respective tab.
In addition to the description provided in this tutorial you can find the full HTML documentation of the standard library available via »Help«-»Standard Library qfs.qft...«
|Inspecting the Standard Library|
In addition to inserting procedure calls from the Standard Library, it also can be helpful to sometimes have a look how certain things organized or implemented.
qfs.qft, which is located in the
qftest-4.7.1/includedirectory of your QF-Test installation.
||Figure 16.1: The Standard Library|
You can see there is one main package
qfs that contains further specific
qfs package helps to easily identify the packages belong to
the standard library.
The specific packages cover very different areas of utility procedures described in more detail further below.
Within nearly all of the procedures of this library, you'll notice that the
$(client) is referenced. This is the standard mechanism for creating
independence from a specific SUT. Here, the library assumes that the
test-suite which uses the library will set a value for
to using any procedures.
|Selected Packages and Procedures|
|Last update: 09/19/2019
Copyright © 2002-2019 Quality First Software GmbH