• info@helpingtesters.com
  • helpingtesters

TestRail Tutorial – Test Case & Test Management Testing Tool

August 18, 2017
TestRail, TestRail Tool, TestRail Test Management Tool

Now a day software plays a vital role in our lives in the form website and mobile application. But have you ever thought, How this software came into existence? In the Software Development cycle, Testing play one of the Vital role in making the software Bug free. And to manage all this testing task we need the help of a Test Management Tool. There are many test management tools available in the market but TestRail is one, which is solely responsible for managing the testing activity within the scope of a single application.

Topic of TestRail Test Case & Management Tool Tutorial

 

History of TestRail

In the Software Testing Life Cycle(STLC), we can across different activities which are carried out to improve the quality of the product like- Requirement Analysis, Test Plan, Test Case Development, Environment setup and so on. Among all this activities Test Cases preparation plays a very important role in executing of the testing process.

Many of us, prefer writing test cases in excel or shared spreadsheets. But in this era of automation, maintaining test cases in excel sheets is a very old and outdated process. Moreover, there is a greater chance of data loss and it’s much time taking too.

In order to get rid of this problem, Gurock Software, Headquarter in Berlin introduced the Software Test Management Tool TestRail. It is a modern Test Case Management Software for QA and Development Teams. It helps to manage and track our software testing efforts and organize our QA department. Its intuitive web-based user interface makes it easy to create test cases, manage test runs and coordinate our entire testing process. Easily track and follow the status of individual tests, milestones, and projects with dashboards and activity reports. Get real-time insights into our testing progress and boost productivity with personalized to-do lists, filters, and email notifications.

What are the Features of TestRail?

 Efficiently manage test cases, plans, and runs.

  • Graphical representation of the test run and output.
  • Report generation of the test.
  • Integrates with issue trackers like Jira.
  • Boost testing productivity significantly.
  • Get real-time insights into our testing progress.
  • Organize and track software testing efforts

How TestRail works?

1. DashBoard

  • After getting logging into Testrail, Dashboard is the launching page.
  • The Dashboard shows all the project overviews and the activity chart. Clicking on any project will expand projects to review related milestones.

  • When coming to project Overview tab, it provides an overview of the projects, recent project activities, and our todos. We will find the overall test result managed at a central location and the activity chart.
  • It will also display all the test cases passed, failed, Blocked and need retest for this project. Whenever we need to switch to another project, return to the dashboard by clicking the link “Return to Dashboard” in the upper left corner.

2. Todo

Todo section is the central piece TestRail and is considered as the starting point for the testers. What Todo Section do?

  • Makes it easy to track and filter progress
  • Help in assigned tests for team leads
  • Help in assigning test to different users to minimize the workload.
  • Best place for an individual tester to check the task assigned.
  • In order to differentiate the tests grouped by release planning, different color combinations are being used for active, pending and upcoming release.

Todo page is integrated with the standard test run page in order to benefit from the added features such as advanced filters, improved navigation and much more.

3. Milestone

  • As we known we can create and manage multiple projects on Testrail and many teams can also work on multiple releases, iteration or sprints during a project.
  • We can use the Milestone tab for creating the milestone for different projects. We create milestone for important events in the project such as an alpha and beta deployment other than different releases.

 

  • Whenever we are creating or editing a milestone we can set a Due Date and this helps in keeping a track of which milestone is coming next. We can enter the Description and can also mark the Milestone is Completed to better focus all active and upcoming milestone.

    • In addition to managing our project in the testing milestone in Testrail we can also assign test runs and test plans to a specific milestone, so we can easily track a milestone progress and view all test milestone at a glance.
    • If we are working on multiple project versions of the same time, milestone makes it easy to track the test results for different versions in parallel.
    • So when we select a milestone we can see the status of the milestone at a glance. And also we can see the links of results of all test runs.

 

4. Test Runs and Results

  • Managing test cases is an important part of an application.But having great support in executing test run to enter results and track the progress of software test is equally important.
  • Once we have added a few test suits and entered test cases we usually want to execute the test and record the test results. And to do this we can start a Test Run in the application.
  • The Test Runs and Results tab displays all runs which are currently active for this particular project. A test run always starts with a particular test suite and this is an important concept in a test rail, as it allows us to start multiple tests run for the same test suite over time.
  • So, whenever we need to test a new version of the application, we can start Test Run on your existing test cases. We can also execute different Test Runs for different platforms (mobile and web).

 

  • We can start a test for a project from “Add Test Run” option. Initially, we need to provide the Name for the Test run. After that, we need to provide some additional details for the test run like:
    • Milestone: To link a Test Run to a Milestone, you can simply select the milestone(e.g; Release 1, Release 2, etc) when you add or edit the test run in the application.
    • AssignTo: We need to assign the assignee who is going to run the test.
    • Description: A bit description of the test run.
    • All test cases include (select cases): By default, all test cases get included in the test run. But in some cases, the user can select test cases from the whole test cases or all cases and can perform the test run.

  • It also provides with multiple filter options to selecting test cases quickly and effectively. The different filters which test runs provide are-
    • Estimate
    • Forecast
    • Milestone
    • Priority
    • References
    • Section
    • Title
    • Type
  • After setting up the filter, we need to perform the search by clicking on the Set Selection button. This will select all the test cases based on the filtration done. 
  • After the test run is created, we are redirected to the Test Run Page and it shows us the overall status of the test run and status of all individual test. To verify a test and enter a test result we will need to select a test case and open it.
  • Once we opened test cases, we can view all the details of the test cases which need to be verified, which includes Preconditions, Steps, and Expected results. Once the test has verified, we can add test result from the Add Test Result option. Here we need to add the Status (Failed, Blocked, Pass, etc) and the comment for the test.
  • Another interesting part is the availability of some other options like- Assign To( Assigning to another person for re-verifying) Version, Elapsed and  Defects( adding the defects id from different bug tracker like-Jira, Firebug, Bugzilla).
  • Once we added the test result, we will be redirected back to the Test Run page with the Test result updating for the specific test run. The test result will also get reflected in the pie chart.



5. Test Suites and Cases

  • Test Suites and Test Cases are important aspects of Testrail. And they explain the single application functionality or requirement which we need to verify.
  • A project can have 1000 or more test cases per project, Testrail allows us to group the related test cases into so-called Test Suites. 
  • It is generally recommended the group the test cases based on the functionality/module or based on the web pages. Creating Test suites helps in managing the test cases and also helps in test runs.

Let’s see, how we can add Test suites and Test cases

  • In this tab, we can create a test suite from the option Add Test Suite. Once the Test Suite is created, click on the created test suite.
  • Testrail also allows creating Section under which the test cases are to be added. We can create Section from Add Section.  And going further we can the Test Cases from Add Test Cases option under that specific Section.

  • When creating test cases, we need to fill the following fields:
    • Title: We need to give the title of the test case.
    • Section: By default, it will select the section under which this test case is written.
    • Type- It defines the type of testing to be done like- Functionality, Usability, UAT, Regression and so on.
    • Priority: We need to set the priority for the test cases. As a result, we can perform the test run for this test cases with priority.
    • Estimate: Need to fill the estimation for the task.
    • Milestone: We need to select the specific milestone for which this test case is written.
    • Reference: It is a very important field for keeping a track of the defect with the bug tracking tools like Jira. We need to add the defect number in the Reference field.
    • Description: Need to provide a detailed description of the task.
    • Precondition: Need to mention the pre-conditions that need to perform before the executing this task.
    • Steps: Need to mention the step of reproducing of the defect/task.
    • Expected Result: It is also an important aspect of the test case. The test result depends on the expected result a lot. We need to compare the actual result with the expected result and change the status of the test result accordingly.



6. Report

Software testing reports in Testrail are just as important as running tests. Testrail report area with support for generating, scheduling, sharing and emailing reports with built in templates. The report consists of actual information of the test. A testing report with lots of statistics, but without any actionable conclusions is not that valuable. TestRail’s software testing reporting feature has been designed to provide you with relevant information at just the right level of detail.

Summary

Testrail is one of the most important tools for software test management which help in managing testing activities which includes- Milestone creation, Test cases preparation and binding them together in a single test suite, helps in performing the test run for the created test suite/test cases and generate report base done the testing performed.

About the author

Asim Mondal author

Asim is ISTQB certified tester, expert in QA/Testing with a Master's in Computer Application, whether it is Mobile testing (Android, iOS and windows) or website testing he always lead the way in IT systems efficiency and a swift resolution of issues minimizing his employer’s risk.

Leave a Reply

Your email address will not be published.