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.