TestRail Reviews

Most valuable features are the ease of organizing test cases and a great API for sending results from automated test run results into the database.

We don't have to take care of test case results in time. They are automatically added into TestRail (TR) on a per case basis, so you have the test results history.

Only a few small ones. Reporting could be more flexible regarding repeating reports. You have to basically repeat the same report run, but then you have two reports. An old one and a new one. A 'refresh' option for reports would be very useful. This way you would have a report but just need to refresh its data when needed. Also, more flexibility in adding custom fields and their placing around the test case form would be beneficial. For example, sometimes I can't place a custom text (paragraph) field in the exact spot that I was planning. Again, nothing critical, just a few small improvements.

For about nine months now.

No issues with stability in the last nine months that I've been working with TR.

No issues with scalability so far.

I haven't used their tech support directly because all I needed was info that I was able to find in their knowledge database.

I used Zephyr, but didn't make the switch. My new company was already using TR when I joined it.

Not applicable. It was already set up when I joined.

Use TestRail Cloud (online TR hosted server) and don't worry about maintenance or scalability. It saves a lot of cash and time.

Yeah, Zephyr, Redmine, etc.

It is great for manual testing. However, it is awesome for automated testing and integrations with most used testing frameworks.

I use TestRail for creating test plans, test cases, and generating reports.

The product’s most valuable feature is the UI. The structure of test cases is easy to understand.

The platform needs improvement regarding performance and creating links.

I have been using TestRail for three years.

I rate the product’s stability a seven out of ten.

We have 30 TestRail users in our organization. I rate its scalability a seven out of ten.

I rate the initial setup process a nine out of ten. It takes 20 minutes to complete.

The product has a reasonable price in terms of the features.

I recommend TestRail as it is the top test management tool. I rate it a nine out of ten.

• Suite management
• Integration with Confluence and JIRA
• Making runs and workflows

A lot of cases can be organised with workflows and become scenario-based.

• Case writing UI
• Better prediction of text

More than one year.

None which I can remember.

No.

The database structure and exploration tool. The API to support integration of the homemade automated testing tool.

This product completes our production line based on continuous integration (using Jenkins) by acquiring all tests results, manual and fully automated into a single platform, which is connected with our bug reporting system (Trac). It offers a full view of test campaigns for each product/version we develop.

The TestRail API to integrate reporting of automated tests is complete, but requires many requests to identify the appropriate entry.

The main room for improvement is in the reporting: It provides templates which are not well adapted and introduces new ones that are rather complex.

Four months.

No issues so far.

With a few users only, but already thousands of items in the DB, we have no issues so far.

Quite good and fast for my interactions with them.

No.

I did not manage it myself, but it seemed straightforward (using the officially supported Linux version).

Pricing for small teams seems correct with respect to competitors.

JIRA/Enterprise Tester: Felt less user-friendly and more complex to start with. Also, it was less adapted for coupling with a homemade automation testing tool.

TestRail is a very user-friendly product to manage test cases. It integrates easily to automation systems and most common bug tracking systems.

It is not the Holy Grail, but has many interesting, useful features.

The feature that is of most value is the ease of use. You don't need to follow complex procedures to create a test run, test case, etc.

Before we used TestRail there were no, or only a very small number of, test cases written. Now, because it is easy to use, there are many more test cases written.

It would be nice if they would add an export to Word.

We have been using this product for about one year.

We never had any issues with stability.

We never had any issues with scalability.

I’m rating technical support a nine out of 10.

We used TestLink. The reason we changed was that it was rather complex to use and there was no way to indicate at what step the case failed.

The initial setup was straightforward.

I can’t answer this question because I’m not the one handling the financials.

I can’t answer this question because the choice was made before I came to this firm.

The advice I would give is just do it.