Information

Published
Version 1.0 - Mai 2018

Categories
Integrations

Products
Polarion ALM
Polarion QA
Polarion Requirements

Price
Contact Us:
info@garantis-solutions.com

Ask Garantis IT Solutions

Direct Access:
+44 (0) 118 343 1584

Garantis IT Solutions is happy to answer your questions:
info@garantis-solutions.com

What our Customers Say

• Customer stories
• Users' opinions for our products

Integrating Polarion ALM with qTest

Overview

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

Why you need it? Benefits How it works The Teams - Collaboration Workflow What you can see in Polairon ALM What you can see in qTest What you can see in qTest

Why you need it?

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

• 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

1. The Requirements are stored and managed in Polarion ALM.
   
2. Test Cases can be created in both systems - Polarion ALM and in qTest.
   
3. Test Case from Polarion ALM are exported to qTest.
   
4. Test Campaigns are managed and executed in qTest
   
5. 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 Polairon, establishes links for traceability.
QA team - executes test cases in qTest, manages test campaigns.

Workflow

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

What you can see in Polairon ALM

• Coverage. - it answers the questions:
  • "does each requirement have a linked test case?"
  • "How many requirements are not veriefied?"
  • "How many more test cases do we need to develop?"
• We respond quickly.
• Suspect links. - it answers the questions:
  • "is there any impact from changed requirements?", "Shall I update some test cases?"

Coverage - Statistics

"How many requirements are not veriefied?"
"How many more test cases do we need to develop?"

Coverage - Missing Test Cases

You can detect early if any of Requirements don't have any Test Cases.

Suspect link

Suspect links highlight potential inconsistency between your workitems. E.g. when you change parent requirement, your child requirements or testcases migth need update.

What you can see in qTest

Our Offer

We begin our client engagement with a careful evaluation of requirements to find the technology which best suits the client’s needs. Garantis IT Solutions provides dedicated services, covering a complete design – from concept to market. We also offer on-demand expert services that can be tapped at any stage of the product development cycle.

Garantis IT Solutions can take up a part of or the complete software development process:

• Concept
• Design
• Implementation
• Documentation
• Testing
• Maintenance