Pivotal Tracker is an agile project management tool for software team project management and collaboration. The tool allows you to plan and track your project using stories.
Your Testlab project can be integrated with Pivotal Tracker to export assets from Testlab to Pivotal Tracker as stories and, to push stories from Pivotal Tracker to Testlab’s project as requirements.
The integration works in a two way manner. First, you have an option to import assets from your Testlab project to your Pivotal Project as stories to be tracked. You have an option to pull requirements, test runs, test sets, milestones, issues and even test cases from your Testlab project. When done so, a new story is created to your Pivotal Tracker project. It is as easy as dragging an asset to your project’s Icebox in Pivotal.
You also have an option to push stories from your Pivotal Tracker project to your Testlab project. This way, you can easily push all your stories from your Pivotal Tracker to Testlab project’s specification as user stories to be verified and in addition, push bugs from your Tracker to Testlab project as issues.
Using Pivotal Tracker with Testlab is an excellent choice for project management. This way you can plan and track your project activities in Pivotal Tracker and in the same time, test, verify and report your implementation in Testlab.
To integrate Testlab with Pivotal Tracker, technically, we use two kinds of integrations:
When a Pivotal Tracker integration is configured, the behaviour of Testlab’s user interface is changed as follows:
To get started with integration follow the steps described below. If you have questions about these instructions or any problems with the set up please feel free to open up a support ticket in Testlab. We are happy to help you in your setup!
When you are using Pivotal Tracker for tracking your project tasks, it is essential that you can also track things related to Testlab. For this, you can expose assets (Requirements / user stories, issues, milestones, test runs, test sets and test cases) from Testlab to your Pivotal Tracker. You can import assets to your Pivotal Tracker project as stories just by dragging them to your Icebox.
Configure an integration your Pivotal Tracker project as follows:
When importing assets from Testlab to Pivotal Tracker the assets are importable as follows:
|Testlab asset||What can you import|
|Requirement||All non-deprecated requirements excluding folders.|
|Defect||All issues which are not yet resolved or closed.|
|TestRun||All test runs which are in not started or started status. Finished or aborted test runs are not exported.|
|TestSet||All test sets.|
|TestCase||All non-deprecated test cases.|
As an example for the above for hosted Testlab mycompany.melioratestlab.com, you can expose Milestones from your Demo project by configuring the Other integration as follows:
If you prefer to push stories from Pivotal Tracker to your Testlab, a Web Hook in your Pivotal Tracker project configuration must be configured. This allows you to push changes of your Pivotal Tracker stories to your Testlab as requirements and issues.
To configure this, execute the steps below.
As an example for the above for hosted Testlab mycompany.melioratestlab.com, you can push changes from your Pivotal Tracker to your Testlab’s Demo project by configuring the following:
This configuration will
When pushing stories from Pivotal Tracker to Testlab, the fields of assets are mapped according to the table below by default.
If you prefer to have these mappings configured for your project please open up a support ticket and we’ll customize them for you.
|Pivotal Tracker Field||Pivotal Tracker value||Testlab Field||Testlab value|
|Story type||feature, chore||Class||User story|
|State||planned, unstarted, unscheduled||Status *||In design|
|started, finished, delivered, accepted, rejected||Ready|
* Workflow status is used for different purposes between these systems. In Pivotal Tracker, status is used to track the progress of the actual implementation of the story and in Testlab, status is used to track the design of the requirement. For this reason it makes not practical sense to map these workflows together. The above mapping only ensures, that when a related story in Pivotal Tracker is started for implementation, the matching requirement in Testlab is also transitioned as ready to indicate it should be ready for testing.
|Pivotal Tracker Field||Pivotal Tracker value||Testlab Field||Testlab value|
|State||finished, delivered, accepted||Resolution||Fixed|
|unscheduled||Status *||Open, Unscheduled|
* The above maps the Pivotal Tracker’s story status to the default workflows for Testlab’s issues. If you’d prefer to have matching workflow visible in Testlab too, you can configure an issue workflow in Testlab side with matching titles (as seen in the table above).
You can integrate your Pivotal Tracker project with Testlab in a way, in which Testlab’s assets can be easily imported to your Pivotal Tracker to be tracked as stories and/or, to push changes of your Tracker stories to Testlab to be created as requirements and issues.
This enables you to track your project tasks with Pivotal Tracker and manage and plan your testing with Testlab.
In Testlab, log in to your Testlab project, select Testlab > Manage project(s)… and choose the Integrations tab. All integrations which can be taken in use by yourself are configured per project from this view.
In Pivotal tracker the integrations and related Web Hooks need to be set up. Check the prerequisities and follow the instructions above in this document to set up the integration at the Tracker side.
From Pivotal Tracker, no data is ever deleted.
From Testlab, when configuring the integration you have an option to forbid asset deletions by leaving “Delete from Testlab” option in the project configuration disabled. When done so, when a story from the Tracker is deleted the possible linked requirement or issue in Testlab is left as it is.
It should be noted, that if configured for deletion, only requirements and issues are deleted from Testlab. For example, if a story in Pivotal Tracker is imported from Testlab’s test run, the idea is, that you want to track the execution of this test run in your Pivotal project. If for some reason, you delete the story from your Pivotal project, the test run in Testlab is not deleted, which probably is preferred.
On the other hand, for user stories and issues (Pivotal’s bugs) which originated from your Pivotal board, it makes sense to purge them from your Testlab too if they are regarded as not needed and they are deleted from your Pivotal project. The “Delete from Testlab” option mentioned controls just that.
In Testlab projects integration configuration you have an option to define the identifier of a (requirement) folder in your project. When a new story is pushed from the Tracker, it is always initially created to this folder.
If a story is a bug and is mapped as an issue in Testlab, issues will be added normally to the issue listing of your project. Issue will get automatically created Testlab specific ID for tracking.
When changes of a story from a Tracker is pushed to Testlab, the linked requirement or issue in Testlab is always automatically tagged with a matching tag. For example, if your story in Tracker is in Backlog the user story in Testlab will be tagged with a tag “backlog”.
In addition, we also set the raw state value of story as a tag. In Pivotal Tracker, stories move between unscheduled, unstarted, planned, started, finished, delivered, accepted and rejected states, which we also add as an tag to indicate the exact state of the story.
With tags in Testlab, you can easily find all Pivotal Tracker pushed stories in specific state by searching with the appropriate tag, for example tag:icebox.
When creating user stories to Testlab the ID, name, description, creator, update timestamp, assignee/owner and requirement class is mapped.
When creating issues to Testlab the name, description, creator, update timestamp, assignee/owner and workflow status is mapped. In addition, resolution is set to Fixed according to the state of the story in Pivotal Tracker.
For both requirements and issues, attached files and all comments relating to the story are pushed to Testlab.
Yes you can! In Testlab, editing views for linked assets will contain a button which enables you to open up the related story from your Pivotal Tracker project.
And other way around, all stories created from Testlab’s assets in your Pivotal Project contain a link to open up the related asset in Testlab.