QF-Test contains some pragmatic test management approaches, like creating a test-case overview or documenting test-cases within QF-Test. In bigger projects it might be neccessary to make use of an own dedicated test management system to track the development status of test-cases or to link test-cases and their results to defects, use-cases or features. Besides support for planning of test-cases and tracking their results a test management system could also contain a test execution engine, which supervises the occupation of test-systems during different test-runs.

As QF-Test doesn't come with all of those features though continously improving in that area, it is very easy to integrate QF-Test with such a test management or test execution system using the QF-Test Batch mode or the QF-Test Daemon mode. For more information about the Batch mode or the Daemon mode, please see chapter 16.

The following chapters describe some exemplary solutions which we provide for established test management systems. If you cannot find your test management system in that list, please contact us or our mailing-list to get hints about a possible integration approach.

The current integration of QF-Test and HP TestDirector for Quality Center utilizes the built-in VAPI-XP test type of Quality Center. It is intended to be an automated test-case for any test-tool. QF-Test comes with a template file for the VAPI-XP script, which is qcVapiXPTemplate.txt, see qftest-3.4.7/ext/qualitycenter. This script can be used as template for all QF-Test tests in Quality Center. Please see subsection 19.2.2 for a detailed step-by-step description.

The QF-Test template VAPI-XP script employs an external worker VBScript script, called qcTemplate.vbs. This script is also part of the QF-Test distribution (see qftest-3.4.7/ext/qualitycenter) and has to be adapted to your specific needs. So we encourage you to copy that file to a project specific location and adapt it according to your needs.

The worker script launches QF-Test in batch mode on each test system locally, i.e. it has to be accessible for each test system. As the test suite files and the configuration files have to be available on the test system too, we recommend to put all those files on a shared network drive or into the version management system.

After the execution of the test the run-log of QF-Test will be appended to the test instance as well as the status of the test will be set to the result.

You can also change the worker script to make use of a daemon call (for details about the daemon mode, please see chapter 40). In this case QF-Test will establish the network connection to the test system and launch the test by itself. In case of the normal batch call Quality Center establishes the connection to the test-system and triggers the local QF-Test installation to perform the test. If you make use of the daemon call, the worker script has to be located on the Quality Center system, but the test suite still needs to be accessible on each test system.

If you do not make use of VBscript in your project, feel free to port the QF-Test demo scripts to JScript or any other supported language.

The following figure shows the VAPI-XP test-case in Quality Center:

		Figure 19.1:  QF-Test VAPI-XP test-case in HP QualityCenter

Please perform the following steps on the test systems:

• Copy the template worker script from qftest-3.4.7/ext/qualitycenter/qcTemplate.vbs to your project location and rename it to a proper name. We recommend to use the same path on all test-systems. Perhaps you should use a shared network drive.

Please perform following steps in Quality Center:

• Start Quality Center.
• Create a new VAPI-XP test-case.
• Copy the content of the template file qftest-3.4.7/ext/qualitycenter/qcVapiXPTemplate.txt into the Script Viewer's text area.
• Change the pathToModule variable in the script to the location you have copied the worker script qcTemplate.vbs to.
• Change the testSuiteFile variable to your desired test-suite file.
• If you want to execute one specific test, you can also change the test variable to the desired test-case name.
• Change to the "Test lab" section in Quality Center and add the test-case to the execution grid. Then launch the test-case.
• Now Quality Center should start the test run on the test system.
• After the test has terminated, the run-log of the test will be uploaded as attachment to the test instance and the status of the test will be set to the according result.

Please read the comments in the script carefully, because you can also use test-case specific settings optionally.

The current integration of QF-Test and the TestBench consists of two parts:

• Creating a QF-Test template file using the TestBench interactions.
• Importing QF-Test results into TestBench.

You can find a wrapper test-suite for launching TestBench scenarios in qftest-3.4.7/ext/testbench/testbench.qft.

The following section provides a short overview about the integration concept.

After planning your tests and designing the interactions in the TestBench, you can create a template QF-Test file using the QF-Test export plug-in for interactions. Imbus will provide all required information, how to install this plugin.

After exporting the interactions you will find all interactions as procedures and their structure as packages in the QF-Test file. Now you can start recording the respective steps in QF-Test and fill the empty procedures.

The completed file has to be saved in your project-specific test-suite folder, because this file should be used as input file for the test execution later. We recommend to use a project-specific location, perhaps a shared network drive or the version management system.

The tests will be executed by a wrapper test-suite which is capable of reading the iTEP export files of the TestBench. This specific wrapper test-suite has to include the template test-suite which has been created during the export of the interactions (for details see the previous chapter subsection 19.3.2).

QF-Test provides a sample wrapper at qftest-3.4.7/ext/testbench/testbench.qft.

Before you start, you have to export the required test-sets from the TestBench using the iTEP export plug-in.

After exporting you can launch QF-Test using the wrapper test-suite. The wrapper contains variables specifying the iTEP export directory, the QF-Test run-log directory and the iTEP results During the test-run QF-Test will create one run-log per test-case and a summary run-log containing all test-runs at the end.

When the test-run has been completed, you can import all those results using the iTEP or iTORX import plug-in into the TestBench. The single QF-Test run-logs will then be attached to the test-instances.

The current integration of QF-Test with the open-source tool TestLink consists of two parts:

• Generating template test-suites for QF-Test from the planned test-cases of TestLink.
• Importing QF-Test results into TestLink.

The current version accesses the database of TestLink directly. This approach requires a JDBC database driver to use the provided scripts. You can download those drivers from the web page of their providers. At the moment a separate extension API for TestLink is created and the integration concept will be ported to this API, if it is stable enough and has enough features. Then no direct database access has to be performed anymore.

Exporting the planned test-cases including its test-steps from TestLink to QF-Test supports the test-creator to implement the test-cases exactly as planned.

Importing the test results into TestLink provides a better overview over all executed manual and automated tests-cases in one tool.

Note Test results can also be uplodated to TestLink without exporting them before. Therefore you have to take care, that the ID of the test-case from TestLink is part of the test-case's name in QF-Test. The name has to be called like this: <TestLink-ID>: Name of the test-case.

QF-Test offers the capability to generate template test-suites following the same structure as the planned tests in TestLink to guarantee a synchronized structure of automated tests and test planning.

In the QF-Test file you can find one 'Test-case' node per test-case and one 'Test-set' node per suite from TestLink. If you have specified the fields "Steps" and "Expected Results" of a test-case, the generating-script will also create an empty 'Test-step' for each test-step in the according test-case. The expected result will be shown in the 'Comment' attribute of the 'Test-step' node.

Now the template test-suite has to be filled by the test automation engineer with the according steps by adding QF-Test steps to the generated 'Test-step' nodes.

In case you want to export test-cases from TestLink you should perform following steps:

1. Copy the folder qftest-3.4.7/ext/testlink/export to a project-specific location.
2. Open the launcher script you want to use with a text editor. The launcher scripts are exportTestLinkToQFT.bat for Windows and exportTestLinkToQFT.sh for Unix.
3. Adapt the paths of the variables JAVA, QFTDIR and TESTLINKINTEGRATOR.
4. Open the file TestLinkDBIntegrator.py with a text editor.
5. Adjust the variables dbdriver, conncetionstr, dbuser and dbpass according to your database connection.
6. If you want to export custom fields from TestLink, also adjust the variable custom_fields.
7. Run the adapted export script, like shown below.

exportTestLinkToQFT.bat --testproject projectname --targetsuite /path/to/testsuite.qft

Executing the QF-Test tests can be performed as usual. But you should create a XML-report at the end of the test-run, because the import mechanism is using this report. Therefore you have to use the '-report.xml' parameter during test execution. If you create the reports via the GUI, you have to check the checkbox 'Create XML report'.

Note In case you did not export test-cases from TestLink the ID of the test-case from TestLink has to be part of the test-case's name in QF-Test. The name has to be called like this: <TestLink-ID>: Name of the test-case.

qftest -batch -report.xml reportFolder testsuite.qft

After creating the XML report file, you can upload the results to TestLink.

The import nechanism creates a new build for every test-run. The build number of TestLink will be created by the run-id of the QF-Test report. You can change the run-id, by setting the parameter '-runid' during executing the tests.

In case you want to import test-results into TestLink you should perform following steps:

1. Copy the folder qftest-3.4.7/ext/testlink/import to a project-specific location.
2. Open the launcher script you want to use with a text editor. The launcher scripts are importToTestLink.bat for Windows and importToTestLink.sh for Unix.
3. Adapt the paths of the variables JAVA, QFTDIR and TESTLINKINTEGRATOR.
4. Open the file ReportParser.py with a text editor.
5. Adjust the variables dbdriver, conncetionstr, dbuser and dbpass according to your database connection.
6. If you want to export custom fields from TestLink, also adjust the variable custom_fields.
7. Run the adapted import script, like shown below.

importToTestLink.bat --testproject projectname --resultfile qftestReport.xml --testplan testplanname --tester tester

Last update: 04/23/2012 Copyright © 1999-2012 Quality First Software GmbH