Introduction
From past few years, agile process became the core of the software development process. In this process every phase of the software development life cycle (SDLC) moves in parallel.
Requirements pushed by client, development corresponding to the requirements, and testing on the developed section all goes in parallel streams.
Testing team is responsible to reform the raw requirements from client into executable test cases and testers have to execute the test cases as well as they have to file bugs for the failed scenarios. In the meantime if the requirements keep on changing and it becomes very difficult to recreate and modify test cases as well as to manage older requirements for reference.
To make tester’s life easy, so many tools were introduced (Pivotal tracker, Podio, JIRA, Test Rail etc.)
Test Rail is the one which provides the facility to manage the test cases in the best way. It also provides the privilege to the tester to execute test cases and file bugs into JIRA corresponding to the failed test cases.
Test Rail
Now, when it comes to managing test cases and performing actions like execution, modification, and bug reporting for the failed test cases, “Test Rail” is the best tool to do all these actions. This tool can integrate perfectly with JIRA and provide facility to testers to create JIRA tickets directly from Test Rail. In addition, it is very easy for a tester to map the failed test cases with the JIRA tickets with the help of this tool.
Starting with the basic flow of Test Rail
Login with valid credentials.
After login in the Test Rail, user will see the dashboard containing a graphical representation of the status of all projects along with the links of the projects from where users can go to the corresponding project’s test cases.
Now, please see the screenshot to analyze the basic modules for a particular project:
We have to deal with test case creation and execution so we will go ahead with Test Cases and Test Runs:
By clicking on the Project name the user will land on the page which contains the test cases for that project.
Now, for executing the test cases of selected modules so users can just create a new test run for that and select all the test cases from the list of cases which he wants to execute:
Now, after adding the test cases to a test run, comes the execution and bug reporting. Meanwhile, user can mark the status of test cases according to the test result:
Now, if a test case fails, then users can create a JIRA ticket from Test Rail itself.
If a test case fails, then change the status corresponding to the case as Failed.
Thereafter, click on Push in the displayed popup. Then create a JIRA ticket from there so that the test case gets automatically mapped on the ticket.
This is all the basic functionalities and uses of Test Rail.
Note: Please refer to the screenshots for better understanding.
