What is the TestRail?#2
In this article, we will learn about the main elements of TestRail. In the previous article, I gave detailed information about TestRail. The difference in this article is that it contains information that will help us to use TestRail more dynamically.
1. Dashboard
After logging into TestRail, the Dashboard page welcome us. This part has been desing simple and dynamic.
You see your all project on this page. There are Graphic, Projects, and Todos.
- Graphic
The graph shows the number of transactions in the projects daily. This graphic shows all projects and all members’ activities.
- Project
We choose the project we want to work on from these fields. From the headings under the project names, we can reach the location we want to go directly and start working.
- Todos
Todos field shows the actions to be taken on the person. In these fields, we see the number of test cases that are not “Passed”.
2. Milestone
In this field, the date range of the tests to be performed is known. For example, suites that need to be done in sprints can be added to these parts. The use of this area may not be suitable for every project. I would not recommend adding it for tests that are not exactly timed.
Step 1: Fill in the milestone’s property
Name(required), References, Parent, and Description
You can find more details about the property from the TestRail document. The only place that differs in this section is the References area. This part is where the connection of the relevant case with Jira is made.
Step 2: Select Start and End date
Step 3: Click “Add Milestone”
After adding the milestone, you can see your milestones on the Milestones page.
3. Todo
When a test case or test run is assigned to a user, it appears on the user’s to-do list. Each user has a to-do list for each project assigned to them. The dashboard provides a quick view of the user’s to-do task for all projects. The to-do section can also be used to view the to-do list of other team members or the entire team. It provides an easy way to see individual team members’ workloads and progress.
In this area, the person sees the tasks that are waiting for him. For the jobs to appear in this field, the “Assing to” field must be filled in when changing the status.
You can see the tasks whose status are “Untested, Retest, and Failed”.
4. Reports
TestRail supports multiple reporting. It supports Test Case and Test Execution Reports. Generate a detailed summary report for projects, milestones, plans, and Runs. Track the workload of the entire team. It supports Cross Project Report as well.
Reports are generated from the “Test Runs&Result” field and listed in the “Reports” field. For which “Test Run” you want to generate a report, you can create a report specific to that run.
When you click on the report type you want to select, you can create a report by filling in the relevant sections and specifying the properties in the window that opens.
4.1 Type of Reports
TestRail supports some reports in different groups as explained below;
Cases
- Activity Summary: Shows a summary of new and updated test cases.
- Coverage for Reference: Indicates test case coverage for references in the coverage matrix.
- Property Distribution: Priority, Creator, Template, Type, etc. Shows a summary of test cases grouped by attributes.
- Status Tops: Shows test cases with the highest amount of results for selected cases, grouped by case.
Defects
- Summary: A milestone shows a summary of the defects found for test plans or test runs.
- Summary for Cases: This shows a summary of defects found for test cases in the coverage matrix.
- Summary for References: Shows a summary of the defects found and their test cases in a coverage matrix for references.
Results
- Comparison for Cases: This shows the results of test cases in the coverage and comparison matrix.
- Comparison for References: This shows the result of test cases in the coverage and comparison matrix.
- Property Distribution: Shows a summary of tests grouped by a selected attribute for a particular project, milestone, or test run.
Summary
- Comparison for Cases: This shows the results of test cases in the coverage and comparison matrix.
- Comparison for References: This shows the result of test cases in the coverage and comparison matrix.
- Property Distribution: This shows a summary of tests grouped by a selected attribute for a particular project, milestone, or test run.
Users
- Workload Summary: This shows the current workload for users of the entire project, specific milestone, or test runs.
What are the Advantages & Disadvantages?
Advantages:
- Understandable Interface
- Full integration
- Drag & Drop with Screenshot Support
- Test Report
- JIRA & Issue Tracker
- Test Plans
- Platform Configurations
- Batch Editing Cases & Adding Results
- Amazon advanced technology partner
Disadvantages:
- Not an open-source
- No Requirement Management
- No External dashboard
TestRail supports more than 100 plugins to connect different software to make it easy to work with. A wide range of add-ins makes it universal across the globe — JIRA, Bamboo, HipChat, BugZilla, egg Plant, Cucumber, Jenkins, Selenium, etc.
Considering these advantages and disadvantages, you can use TestRail in your projects. In my opinion, the biggest feature that distinguishes TestRail from other tools is its easy interface. The user can learn a lot of features with a little tampering.
As a big mistake, TestRail is compared to Jira. We can do a lot of things in Jira that we can do in TestRail. But TestRail is produced as a “Test Management Tool”. Therefore, it is necessary to consider only these parts when making comparisons. In Jira, on the other hand, the “Test Management” field is a feature it contains. The main purpose of Jiran is agile project management.
