Item: TestRail
Rating: 5
Author: Lisa Krol

Use Cases and Deployment Scope

We use TestRail as a Test Case Management system. We are able to store test run results from our UI and Backend tests as well as run reports easily to gather data to present to the wider organization. We also keep our manual test cases within TestRail. We have multiple test tools that we are able to integrate with TestRail and then integrate TestRail with Jira.

Pros and Cons

Manual Test Cases
Organization
Easy Reporting

Outstanding user bugs
UI is clunky
Things are not where you think they would be

Return on Investment

We are able to easily pull reports any time management would like to see them
Jira integration makes it easy to attach to stories/defects and save time
A quick overview at the system's health as a whole is easy to see from TestRail

Key Insights

Do you think TestRail delivers good value for the price?

Yes

Are you happy with TestRail's feature set?

Yes

Did TestRail live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of TestRail go as expected?

Yes

Would you buy TestRail again?

Yes

Other Software Used

ReadyAPI, Jira Software, Jenkins

Likelihood to Recommend

TestRail is fantastic for being able to store test cases, test runs, test results, and fairly easy reporting. Test case writing in TestRail is straightforward and easy, although can be repetitive.
As a periodic user, the UI/UX is clunky. Things not where you think they would be, sorting and filtering works - sometimes, outstanding defects and support cases linger for quite a while.

TestRail - What it does good is great, but can leave you wanting more.

Overall Satisfaction with TestRail