Saves us a ton of time/money in testing, helps our process stay consistent, and makes it faster to bring up new employees.

Easy and simple way to build a QA process, plus it's web-based, easy to admin, and has a simple UX that even our QA co-ops can follow for manual test. Has scaled well with our team.

Not much to not like. Works as advertised but doesn't seem to tie easily into automated testing, maybe that could be an add on in future.

Working on a Global team, TestRail enabled everyone to have a seat at the Test Case management/creation table. Editing existing test cases was very easy to do, and the GUI makes it easy to find any existing Test Case you are looking for.

First of all, TestRail is an extremely smarter way to track and maintain test cases than using Excel. I like how easy it is to create new projects, create custom fields, create test runs, and generate good looking reports to submit to your managers. The GUI takes a little bit to get used to, but once you get a hand of all of the key-shortcuts moving around the application is easy!

My least favorite part about this software is the JIRA plug in. In order to see the linked test cases from TestRail in JIRA, you need to have a TestRail account. In my company only the testing team had TestRail accounts, while the rest of R&D didn't. While it was helpful for me as a tester to see the linked test cases on a JIRA bug, when we started off with TestRail we had assumed everyone in the R&D department would be able to see this information so we could be more transparent in our testing. My company was not willing to pay for 100 TestRail accounts, so this was a bummer. If yours is then TestRail might be right for you!

We believe that testrail is basic like any other test case management system, features are fairly generic, workflows are fairly dated. However UI is good, probably due to the app being basic. We use it because teams have already comfortable with it, but by no means is this a tool that can solve new development methodologies such as continuous integration test management. If you understand the tools limitations, then may work for you, but we find it to be lacking and at this stage have stopped integrating our CI test runs into the tool.

TestRail's simple UI and functionality is straight forward. Easy for people to jump in and use the tool, assuming that the tool fits Dev/QA's team workflow and method of usage. For the administrator, access is easily manageable, and provides multiple categories for restricting access and defining user roles within the organization.

TestRail is no different than other test management systems, beside the front end and UI benefits. TestRail is good for teams who initiate test planning, test case creation, and management specific to older QA management styles. When introducing continuous integration testing into a development/QA' teams methodology, this is where TestRail needs improvement . TestRail does not do a good job logging individual test runs for historic tracking, DB backend cannot handle the data that is pushed to the system, and we often have to delete DB records to help with performance and lookup. Usually without these backend hacks, the system performs very poorly and is slow. TestRail may be good for teams that have not adopted advanced development and QA practices, but if teams want to integrate CI testing with test cases and suites within TestRail this is where we find it to fail.

TestRail can be a helping hand to the QA engineers. It can now be integrated to JIRA for easier project management and testcase management, User need not to keep track of both of them seperately.

-TestRail provides easy management of test-suites, test-cases, test-runs. Easy management for maintaining agile methodology in the project. -Feature to export/import files for test-cases from xml, csv and xls files. -The provision to define milestones can be useful for maintaining release-wise goals. -The User can define the expected duration and priority for a test-case. - The representation and reporting are the best part of this software, the user can see the progress of the test-run in various formats as pie-chart.

- Test results should be editable as required in some cases.

i have using this tool for my every day test execution before this i was using our own company proprietary tool and then we switched to TestRail as we switched to agile methodology. i have found this quite useful in agile environment. it is scalabe and can be customised accordingly to suite the customer/test requirement. it is now integrated to our companies other tools like JIRA(bug tracker tool),github,automated test suites, bitbucket etc and many others and is working flawlessly. Reports generation and tracking the various result is quite simple and have real time insights for these with this tool. We can easily link our test cases, requirements, use cases and stores using this. Really its a great tool with so many functionalities and i love it. it increase the team collaboration in a great way

When I started to use it it was a relatively good test management tool, but in the second year it turned into a day-to-day struggle, I was wasting a lot of time writing and editing test cases - one of the key job characteristics of the QA. It's important to mention that I am not using TestRail for almost two years, and I hope the things got better. But honestly, I wouldn't risk to go back again.

The test suites and test case structure were good and easy to navigate.

The small tiny bugs that appeared every day and bothered our work. Things like the inability to open a screenshot in full-screen with 1 click.. To do that I had to open it on a new browser tab which was very annoying. And plenty of other similar issues that were arising day by day. This was the reason for switching to another test management system.

Compared to other test case management systems TestRail is relatively easy to set up and configure and maintain. The online documentation is readily available, concise and thorough with useful links to further information. The UI is familiar enough to users of other commonly used test management systems that they don't take long to feel comfortable with TestRail, making implementation and adoption easier. The vendor support is quick and helpful.

It would be helpful to have more examples of how to realize the effectiveness of Milestones versus Test Runs and creating Test Case Templates. All of these are configurable within the UI however it takes a lot of trial and error to find how to make use of these features to best effect. Fields can be customized but some of the choices for required fields seems unnecessary, such as "Estimate" for test case. Adding the option to enter a "Description" or "How to Use This Field" for custom fields would be a useful addition as well.

TestRail allows us to manage our test cases with great Jira integration.

Some of the admin was a bit cumbersome when we first started such that there wasn't a good split between the person that administers the accounts and who pays for it.

In my mind TestRail is the best test management system you could get on the market! During running education initiative I've always used it with the students for learning purposes and this was quite helpful!

After several years in QA and using TestLink and other tools finally I was able to convince management to use TestRail. That was a game changer - easy to use for manual testing, integration with our automation flow and integration with JIRA saved us a lot of work days.

Sometimes I've experienced issue with JIRA integration (we were using Microsoft Active Directory and password to JIRA was changing each month)

Easy to use, simple and straightforward api's to plug into with good documentation. Love this system to use with both manual and automation.

Running test runs are sometimes a pain but you can still manage.

Total: our choice the introduction of Test Rail.

- This is the receipt of real-time test results (creating reports on completely different criteria: Defect Summary, Comparison for Cases, test results for projects / components, etc.) - This is an easy organization and convenient tracking of the load of the testing department (the ability to fully customize the "working dashboard" of the QA department) - Easy installation, deployment and support - "Communication" with the Jira (this is very convenient for regression and autotests) - easy to receive reports on the launch of test suites - beautiful and understandable reports and diagrams- This is an effective management of test cases, plans and test cycles (creating / storing / editing test scenarios, managing test plans, launching test cycles, entering test results) - User-friendly interface (clear, simple, customizable) - Effective management of the following scenario: "technical requirements -> test cases -> overview -> test suite -> test cycle -> results" - convenient storage of test scenarios - This is a significant improvement in the quality of testing (a clear description of test scenarios, their reviews, correlation with requirements, division into areas - all this makes it possible to evaluate both the completeness of coverage by functional tests, and is necessary material for the entire project team)

As one of the drawbacks - until recently, Test Report system was poorly implemented reporting system: scant results on test-wounds, lack of customization of reports, etc.

I used TestRail in my previous company and I am using it in my current one. Firstly, it is easy to use, and all options and settings are close at hand. The structure of test management is also pretty clear. Projects -> Suites -> Sections -> Test cases. Easy to handle and maintain. The whole system is quite simple to integrate with e.g. Jenkins, Cypress, or Jira through the TestRail API. Some products are seamlessly integrated - like Jira, but for some products, scripts have to be written from scratch. Also, thanks to the fact that TR is widely used, there is plenty of help on the internet. Reporting and analysis can be adjusted to the user's needs and set to execute automatically, which can reduce the amount of work. Charts and analyses are easy to understand and can be expanded with the data you need. A big advantage is test parametrization and the ability to recognize and use test data sets. That allows having significantly fewer test cases to maintain. Product is being constantly developed and the customer service is good. As for the downsides, sometimes minor bugs appear e.g. for some time there were duplicated input fields during test case creation/edition - nothing crucial, but it could be annoying. It was fixed two months later and now everything works correctly. The price is quite high and depends on the number of users. All in all, in my opinion, TestRail is the best on the market providing user-friendly testing management.

The product is constantly developing. A lot of functionalities - API, test structure, reports, bug integrations, milestones, etc. Ease of use. Customizability. Integration with other software (e.g. Jira, Cypress, etc.)

Minor bugs. Quite a high price. Rather plain design (not really intuitive)

Able to showcase the test cases executed to improve the overall quality

TestRail helps to manage the test runs and test plan in much simpler way. Adding or changing test plan is allowed during execution is a huge plus.

Unable to recover deleted test cases, as once I accidentally deleted a test suite when I was trying to delete a test plan. Also bulk option to mark test cases Pass / Failed / Blocked is not possible Don't know if there is a option to link Jira test cases.

Coming from a Quality Assurance team which had zero test cases and no system TestRail has become a huge asset. It allows for our team which has members working in a different time zone to continually work independently while still having the entire team engaged.

Right off the bat the software is very easy to use The software allow us to manage our time effectively focussing on running regression tests on any particular task. It has been a useful tool for our Quality Assurance team to prioritize and organize test cases. The fact that we can implement the use of Jira is also a huge plus since this is a tool we also use within our organization.

Not many cons, the only two minor aspects that come to mind are one if you have no knowledge of how to use it does take some time to learn it. However if you have even the basic background on a tool like this the learning time does shorten. The other is the fact that results can only be shared with the registered users, so we are having to take screen shots of results to share with the rest of our company teams.

I'm very happy with it, it's stable, has a slick UI and overall it's a well-built product.

It can cover all of my needs in the entire test life cycle, it's very customizable - I've been adding a lot of my own custom fields to test case templates, for instance. It supports adding shared steps to make your tests more concise, lot of reporting options, milestones, test planning. Pretty much everything a tester needs.

I would like to see an option to add data parameters for my tests.

We are a start up and as we grow, our test cases and test executions are growing. We could successfully manage our tests and executions very well. With a little work on integrating Test rail into our build process, we could get make it part of our build process.

Good way to organize test plans, cases and runs Report is good at test planning level Configuring runs for multiple devices/browsers in run configurations instead of creating new runs APIs are good, Can be integrated into our build process well.

nothing much. may you can support hippa complaint could offering?

Excellent tool for managing the chaos! Much better than passing around emails.

Ownership and organization of issues is my favorite feature. We load data into our cloud solution and issues arises. Using TestRail, we can log issues, provide all pertinent notes and files about that issue in one place. Also, we always know who "owns" the next step on the issue to resolution. The "ToDo" view is also very useful. Todo lets me know what I own across many projects.

Reporting may be available but I don't see it.

Overall, we love the tool and have directed more teams to use it with the caveat that they do not have a lot of reporting needs.

Super easy to use and organize test cases. It works great and allows multiple structures depending on how your team manages test cases

The reporting capabilities are extremely limited. There are some canned reports that you can tweak. We struggle to find what we need without a custom report. You cannot download them as PDF. You need to download them as HTML which is not ideal in most work place scenarios. We can get most of the info we need from the dashboard, but it would be nice to download as a pdf to excel/csv.

We were able to import our large set of tests in just a few short days and be up and running with a more robust tool that offered us an agile transformation.

*customized for any project * easy to get reports from * web based * can import from variety of other tools * good forums for help and ideas

* can easily make it complex for others depending on how you setup * a few known issues that can cause data loss

My team is using this tool to add testcases for all the projects and we uses testplan for the releases.

This tools helps us to organize the testcases and testplan. Adds lot of visibility to the entire team and it’s reporting is very useful

We can’t add testcases in the testplan across different project. Each platform has its own project so when we want to combine the common cases in one testplan, it doesn’t provides us the way.

OVERALL IT HAS BEEN A GREAT EXPERIENCE.

LOVE THE SOFTWARE. IT CAN BE DIFUCULT TO NAVIGATE AND SET UP TEST CASES BUT ONCE THAT IS DONE IT IS EASY TO USE.

IT CAN BE HARD TO SET UP CASES THE WAY YOU NEED TO.

It is easy to use and user friendly. Also I can create the report easily

When moving the test to another test suite will remove the test result history

We are using testrail to manage all of our core tests in the platforms and the experience is excelent.

Easy to configure and use projects, testsuites and testcases. Can manage all projects independent. Integrations are easy for automatize testruns executions .

I miss some integrations with others tools.

Good

It's very helpful to manage all your test cases at one place and easy to document things.

1. If you can add word wrap to test case summary, it would be easy to read instead of hovering on it. 2. If you can add top and bottom buttons , it would be easy to use instead of scrolling over hundreds of test cases to reach top or bottom.