Requirements Traceability Matrix (RTM) with Jira
Requirements Traceability Matrix
Requirements Traceability Matrix is generally known as RTM. The main aim of having RTM is to ensure that all requirements have been tested by executing the test cases. Every user-story has requirements and every requirement is covered by the test cases and each test case is linked with the user-story.
We can achieve it easily by following the way mentioned below. So, let’s get started…
Note: Following tools have been used:
Tool — Jira
Integrated tool for the test management — Test Management for Jira Cloud (TM4J)
- Create a Project on Jira, example “Test Management Project” and the “key” will automatically be provided by the Jira itself that is “TMP”
2. Now create the User Stories in the project according to the given requirements,
Example:
#TMP-2: Customer should be able to log in.
#TMP-3: Customer should be able to reset the password.
3. Now go to the “Setting”. In “Find new app” section, search for “Test Management for JIRA (TM4J)”and install it.
4. You need to enable the installed application for the project to start managing the test cases. To do that, click on “ON”. Provide all the required permissions and save it so that users can maintain the test cases easily.
5. In the “Tests” section, create a folder to maintain the test cases and fill the details.
In the traceability section, search for the User Story #TMP-2 to assign and add it.
Similarly, create all the test cases and assign them to the created user-stories (#TMP-2 & #TMP-3) in the “traceability” tab for all the test cases accordingly.
Test cases for Requirement #TMP-2 are :
- #TMP-T1: Verify that customer should be logged in with valid credentials.
- #TMP-T2: Verify that customer should not be logged in by providing an invalid password.
- #TMP-T3: Verify that entered password should be visible in the encrypted form.
- #TMP-T4: Verify that the login button is disabled when there is no username or password.
- #TMP-T5: Verify that customer should not be able to enter into the application with invalid username/emailAddress.
- #TMP-T6: Verify the message for the invalid username or password.
And test cases for requirement #TMP-3 are :
- #TMP-T7 Verify that clicking on the hypertext link should redirect to the new page.
- #TMP-T8 Verify that new password and confirm new password should be the same.
- #TMP-T9 Verify that customer should be able to click on the “forgot password link”.
It will be visible in the folder as shown in the below image:
6. Create a “Test Cycle” and in the “Test Cases” section, assign all the created test cases (from step-5).
So far, all requirements (user stories) are linked with the test cases and all test cases are mapped with the test cycle (from step-6). Now execute the test cases and let’s generate the reports.
7. To generate the reports, select the “reports” and then click on the “Switch to legacy report” hypertext link. As shown in the below image, various options are provided by the “TM4J” application.
In order to map Test Cases and the User-Story, generate the traceability. Some of the reports are shown below.
Different types of Requirements Traceability Matrix are:
- Forward Traceability: It shows the mapping between Requirements to the Test Cases. It helps us to ensure that requirements are tested thoroughly.
Example: This Forward Traceability can be achieved by using the filters provided by the “TM4J” app. After entering the filters, click on the “Generate” button.
It will provide the Traceability matrix accordingly.
- Backward Traceability: It shows the mapping between Test Cases to the Requirements. It helps us to ensure that only provided requirements are implemented, which means we are not expanding our project by adding extra features.
Example: This Backward Traceability can be achieved by using the filters provided by the “TM4J” app. After entering the filters, click on the “Generate” button.
It will provide the Traceability matrix accordingly.
Conclusion
RTM confirms 100% test coverage is done and helps us to trace and map the Requirement and the Test Cases to ensure that each and every requirement has been covered through test cases. In other ways, no requirement is missed while testing.
