9.1 Activating CI Tool Integration feature in qTest

»Activating CI Tool Integration

»Managing Test Runs and Test Cases submitted from CI servers

Activating CI Tool Integration

In order to receive Test Logs submitted from your CI server and associate them with the builds, you will need to enable this feature in your qTest project.

  1. Access to your qTest project. Click on the Gear icon and select Automation Settings.
  2. Switch on the Activation Status.
  3. Map automation execution results of your CI tools with corresponding qTest values.
  4. Click on Save button.

  Important:

  • Switching on CI Tool Integration will also activate Automation Integration feature.
  • It is required that execution results of your CI tools are mapped with correspondings qTest values. The CI tools' default execution status are as below:

    Jenkins:

    • PASSED
    • FAILED
    • SKIPPED
    • FIXED
    • REGRESSION
    • See this article for further information of Jenkins' statuses.

    Bamboo:

    • SUCCESS
    • FAILED
    • SKIPPED

Managing Test Runs and Test Cases submitted from CI servers

While setting up CI Tool Integration, you have different options to manage Test Runs and Test Cases.

  1. In one Test Suite per selected Release:

    One Test Suite is created under each selected Release on qTest plugin's configurion in your CI server. This is the default option.

    • For Jenkins: Test Suites are named as [Jenkins Project Name] [mm-dd-yyyy], in which [mm-dd-yyyy] is the suite's created date.
    • For Bamboo: Test Suites are named as [Bamboo Plan Key] [mm-dd-yyyy], in which [mm-dd-yyyy] is the suite's created date.
  2. In one Test Suite for all Releases: Test Runs are created under only one Test Suites regardless of selected release in your CI server's qTest plugin configuration.
    • For Jenkins: Test Suites are named as [Jenkins Project Name].
    • For Bamboo: Test Suites are named as [Bamboo Plan Key].
  3. Test Case submitted from your CI server are located under a Module named as [Jenkins Project Name] or [Bamboo Plan Key]. You can optionally select a parent module to contain the CI module. If no parent module is selected, CI module is created under root.