Competence In Application
Lifecycle Management

Integrating Polarion ALM with qTest

Overview

Useful integration to support test execution in qTest without losing traceability and coverage in Polarion ALM.

Why you need it?

• Keep complete V-Model in Polarion, with traceabilty links between Requirements and Test Cases.
• Export TestCases for execution in qTest.
• Import back Test Results and generate Coverage Report.

Benefits

Architects, Developers and QA engineers see the following benefits:

• Preserved traceability and coverage.
• Execution of tests in qTest.
• QA team can use qTest as "tool of choice" for testing.
• System Development team can see results of testing, recieve Bug reports in Polarion ALM.

How it works

• The Requirements are stored and managed in Polarion ALM.
• Test Cases can be created in both systems - Polarion ALM and in qTest.
• Test Case from Polarion ALM are exported to qTest.
• Test Campaigns are managed and executed in qTest.
• Test Results are imported from qTest back to Polarion ALM. Links are created automatically between Test Cases and Requirements.

• Copy Test Cases to qTest.
• Copy results back to Polarion.
• Preserve links in Polarion.
• Execute in qTest.
• View reports in Polarion and in qTest.

The Teams - Collaboration

System Development team - defines Requirements and Test Cases in Polarion, establishes links for traceability.
QA team - executes test cases in qTest, manages test campaigns.

Workflow

• Export this test case to QTest.Test case in QTest.
• Design test run in QTest to test Test Requirement.
• Execute test run in QTest, include software versions.
• Fail this step to create defect.This result should be failed.
• Export results from QTest to Polarion.Test run result in Polarion.
• Check Polarion result shows software version number.Polarion result shows software version number.
• Check defect in Polarion.Defect in Polarion.
• Check links from test run to requirement.Requirement verified by test run.

What you can see in Polarion ALM