Pros from reviewers

• Web-based: TestRail is a web-based software, eliminating the need for local server installation and enabling access from anywhere with proper credentials. This feature makes it convenient and accessible for users across different locations

• User-friendly: TestRail is known for its user-friendly interface. It provides clear categorization of test cases, test runs, and milestones, making it easy for users to navigate and manage their work

• Efficient tracking and maintenance: Compared to other methods like Excel, TestRail offers a more efficient way of tracking and maintaining test cases. It allows easy management of test-suites, test-cases, and test-runs, which is beneficial for maintaining agile methodology in projects

• Integration with JIRA: TestRail integrates with JIRA, simplifying project and testcase management and eliminating the need for separate tracking. This integration saves time and improves workflow efficiency

• Detailed reporting: One of the best features of TestRail is its representation and reporting. Users can view the progress of the test-run in various formats like pie-charts, making it easy to track and present data.

Cons from reviewers

• Lack of search and replace function in multiple test cases: TestRail does not allow users to search and replace words in multiple test cases at once, making it difficult to re-use existing test cases with minor changes

• Limited access to JIRA plugin: To view test cases linked from TestRail in JIRA, a TestRail account is required, limiting access for teams where not everyone has a TestRail account

• Frequent bugs and data loss: Users have reported frequent bugs and instances of test data and test runs vanishing or becoming unreachable, causing significant disruption to workflow

• Inability to edit test results: Although administrators can now modify test results, any test modifications must still take place, limiting flexibility for users

• Lack of versioning for test scenarios: TestRail does not support versioning for test scenarios, meaning users cannot see previous changes or have different versions of them.