9.9. Quality Center™ Integration

Table of Contents

9.9.1. Definitions
9.9.2. Creating the VAPI-XP-TEST in Quality Center
9.9.3. Preparing the test instances
9.9.4. Test report

The integration with Quality Center™, formerly known as HP Quality Center™, is implemented via the use of VAPI-XP test, for which we are providing a (VBScript) test script template that:

This covers the basic use of Squish, however the template can and should be updated as the user sees fit. The test script template can be downloaded here: script.vbs

We are describing only a basic use of Quality Center™, some more advanced techniques/use can be found in the official documentation: Micro Focus documentation

The following sections will cover the creation of said test in Quality Center™, how to prepare test instances, and what is reported.

9.9.1. Definitions

Let us first define some of the term that will be use in later sections.

The "Test Plan" module contains what is called a test plan tree. This test plan tree contains one or more folders, called test subjects, that in turn contain one or more tests.

The "Test Lab" module contains what is called "Test Set". Each test set can be filled with one or more instances (occurrences) of test(s) from the test plan tree.

9.9.2. Creating the VAPI-XP-TEST in Quality Center

  1. Head to the "Test Plan" area to create a new test (you might also want to create a new test subject),

  2. Enter a name and select VAPI-XP-TEST as type of the new test,

  3. The default value in the newly opened wizard doesn't need to be modified and pressing 'Finish' will create the wanted base test (Default values are: VBScript as script language and COM/DCOM Server Test as test type ),

  4. Copy the content of our template over the current content of the "Test script" tab of the new test,

    Copy template test script

  5. Add the following parameters in the "Parameters" tab:

    • PathToSquish

    • PathToSuite

    • TestCasesToExecute

    Create test parameters

    You can already set a default value for some of these parameters if that makes sense. For example, the Squish folder path could be the same on all the machines that will run the test.

9.9.3. Preparing the test instances

Now that the test is created in the test plan tree, we can go ahead and add a "test instance" for each Squish test suite that we want to run.

  1. Head to the "Test Lab" area,

  2. Add an instance of our test in a test set,

    Add a new instance of the test

  3. Open the Test instance details and update the real parameters values in the "Execution Settings",

    Setting real parameters value

  4. Repeat previous steps for each Squish test suite that need to be ran.

9.9.4. Test report

The proposed test script is reporting the failures/pass of the major steps:

  • Whether squishserver/squishrunner could be found in "PathToSquish"\bin,

  • Whether suite.conf could be found in "PathToSuite",

  • Whether either all tests successfully passed or one of them failed.

Test report

In addition to these steps a text version of the test result (output of "--reportgen stdout") is uploaded as attachment to the test execution in Quality Center™.