Review for Tricentis Test Management For JIRA
When doing software testing having a good Test Management is key in order to deliver fast results, quality and to be able to scale.
And in order to achieve good Test Management you need a fluid integration with your issue tracker, in my case with JIRA.
I have tried different strategies and various tools to make Test Management and JIRA work but I must say none intrigued me as much as Tricentis Test Management for Jira.(TTM for Jira).
According to the installation page the add on promised to be:
End-to-end test management inside Jira to help QA, development, and the entire business drive quality as one team
In order to convince myself of this I decided to do a full review of the Tricentis Test Management for Jira and see if it fulfills all my expectations.
Getting Started
After installing the JIRA add on ( for this you need admin rights) you can easily see Test Management under project apps
But before using Test Management you first need to give Access ( do not worry this only needs to be done once)
It may be that in some cases just after giving permission Test Management will ask you some details about you. This step is however option since you can also dismiss the dialog
Some additional steps
Following the Getting Started section you should be able at this point to start using Test Management for JIRA from Tricentis. Even so there are some cases where some additional steps need to be performed to finish the setup process.
Once the steps have been done you can Launch and use Tricentis Test Management for JIRA
Requirements
Every good JIRA projects starts with the definition of Customer requirements. And this seems to be also the starting point for Tricentis Test Management for JIRA. As you can see from the below image there are 3 ways to add a Requirement
From the Create Button
By clicking on the New Requirement
By converting an existing issue to a Requirement
List Requirements
After you have created Requirements they are all listed under the Requirements tab
Remove Requirements
In case you added a Requirement by mistake or some requirements have been marked as not relevant from the customer you can easily update the list by removing that requirement from the list using the context menu.
In case you have test cases that are linked to that requirement you will need to remove that links and then perform the action
Link to Test cases
In order to make sure that the Requirement is correctly implemented you need to add some test cases that cover that requirement. This can be done by selecting Link test case from the context menu
As we do not have any Test cases we cannot link them to the Requirements. But do not worry you will add some in the next section.
Test cases
To make sure that a Requirement is fulfilled you need to write test cases to make sure that the Customer receives what it expected. Tricentis Test Management for JIRA offers 2 ways to add test cases
One at a time
Multiple
Adding multiple tests
While adding test cases one by one is a viable solution, being able to import already existing tests is a feature that every Test Management tool should have.
Test Management for JIRA from Tricents offers a flexible import via excel
In order to start the import you need to click on the import button
In case you do not have a template Tricentis provides you one to download
Once you have filled your template you can upload it for validation
Any issue that might exist are shown by the validator
In case there are no error the test are added to the JIRA project
Folders
To be able to keep track of all the test cases it is ideal to group the tests. In Test Management for JIRA from Tricents you can do this with the help of folders.
Via the New Folder option you can add multiple folders
Once you have your folder structure setup you can move the tests to corresponding folder via
In the end all tests should be in folders
Removing Folders
In case some folders are not needed anymore you can delete then via their context menu.
Do not worry about their tests, as they will not be deleted.
Removing Test cases
If you want to remove Test cases this can be done by selecting a test case from the list and pressing delete. In this however the Test case will be removed from the Project so be carefull.
Editing Test cases
Having a structure for the test case is just half of what makes a good test management tool efficient. The other is being able to freely edit the test cases, its steps, its details.
All of these are available in Test Management for JIRA from Tricentis
You can define expected results for each step
You can add multiple steps for a test case
Attachments per step can be added
Steps can be moved
Steps can be cloned
Other tests can be called as tests
Test execution
Once you have defined all of your tests and added them to your backlog you need a way to run them and to keep track of the runs. Fortunately, Test Management for JIRA offers a Test Execution section for exactly this purpose.
Test Cycle
Before you can run your test you need to create a Test Cycle. This defines a period of time for testing that is linked to a specific product version.
Run tests
After the test Cycle has been created you can add Test runs to the Test Cycle. In order to do this the following steps need to be performed
Select the Test for the Test run
Select the Test that you want to run
Perform the test. You can set the status of each test
Add defects. In case there is a defect noticed you can create one directly from the step and it will also be added to the test run
Add comments
Add attachment
Complete the run
Reports
Besides all the structure that Tricentis Test Management for Jira brings in regards to requirements, test cases creation and test execution there is one more aspect that a good Test Management tool needs to have and that is reporting.
I am pleased to say that you will not be disappointed in that aspect either. There is a separate Reporting section in Tricentis Test Management for Jira to provide both technical and non technical team members with an overview of the testing process.
Test Summary
The Test Summary offers a good overview of test case creating and execution. You can select to view the summary based on time, assign or components.
Test metrix
The Test metrix offers a good outline of test case execution based on status. You can select to view the summary based on time, assign,components or version.
Execution progress
To view the evolution of test execution you can use the Execution progress. You can select to view the summary based on time, status or priority.
Traceability Matrix
Last on the reporting side but definitely not least is the Traceability Matrix. This allows you to view the connections between Requirements, Test cases and Test runs. With this view you can make sure that all requirements are covered by test cases and it also gives you the possibility to filter based on test execution status. So to see for example for which Requirement you have failed test runs.
Final remarks
Like any good review some final remarks are in order. And after having a look at Tricentis Test Management for Jira I can say the following
Has a really good build in reporting
Integrates seamlessly into Jira
Easy to work with for both technical and non technical members of the team
Good support and documentation
If you want to give Tricentis Test Management for Jira a try they do offer a 30-day trial.
Have a look and tell me your opinion in the comments.
Top comments (0)