All Collections
Requirements Management
External Sources
Requirements Management using Pivotal Tracker
Requirements Management using Pivotal Tracker

Link stories from Pivotal Tracker as requirements with test cases in TestCollab

Vishal Vaswani avatar
Written by Vishal Vaswani
Updated over a week ago

Presenting the feature that helps you use the project requirements (stories) that have been managed in Pivotal Tracker, to get them linked with test cases, arranged and searched on requirements list and to get traceability matrix generated in TestCollab.

Configuring Pivotal Tracker as source of requirements

To start using stories from Pivotal Tracker, we would fist configure the requirements management settings for our TestCollab project.

Steps to configure:

  • Select Pivotal Tracker as the source of requirements

  • Provide the API token for Pivotal Tracker

  • Select Pivotal Tracker project and story types that are to be used as requirements in TestCollab Project

  • Save the settings

Linking requirements with test cases

Once requirements mapping has been enabled for current project then linking stories from Pivotal Tracker with test cases is simple. The stories are to searched by their title either at the time time of adding test case or editing test cases (this includes bulk update action)

Requirements index

The requirements present in project can be accessed on requirements index.

On requirements index:

  • All requirements are listed

  • They can be arranged in the order of any of the columns

  • They can be filtered on their properties

  • The values on "Linked test cases count" count allow you to automatically navigate to test cases manage page to see the test cases filtered on the basis of linked requirement

Filtering requirements

Traceability matrix for requirements

You can get a traceability matrix report generated for requirements in project to know :

  • Total number of requirements

  • Requirements covered (have test cases linked with them)

  • Uncovered requirements (having no test case associated)

  • Linked test cases count

Please see the user guide article that explains the report in detail

Did this answer your question?