Zephyr Enterprise vs. TestRail

1. Well suited for companies having several applications which need rigorous continuous testing cycles due to periodic upgrades to products/features.
2. Ideally suited for use cases where there is a need to run sanity and regression suites very frequently.
3. It is very helpful to have a traceability matrix across Stories/tasks and easy to link all the test cases to be covered to stories.
4. Variety of reports for Quality Dashboard.

Incentivized

The integration with other tools, and their user friendly layout and design. It's very comfortable to use and is way better than other tools with the Automation Testing tools, thanks to the great API that is included. Sometimes the integration with Jira is a little faulty, but the links to that tool usually work well. It could be cool if it had a better following for the bug items that were registered on other tools.

Incentivized

• Creation of Folders, Sub Folder and Releases for various Teams/Projects
• Ability to create cycles and adding cases to these
• Ability to copy/clone entire test cycles for regression/sanity needs
• Linking of defects to Test Cases

Incentivized

• Beautiful and productive UI.
• Nice filtering system allowing me to find what I need quickly.

Incentivized

• Better Test case Upload Utility
• Ability to quickly map test cases from excel to JIRA fields

Incentivized

• Integration with Jira seems [a] little faulty.
• Increase the API call limit for different editions.
• Better way to trigger automation suites from TestRail.

Incentivized

Incentivized

TestRail definitely saves times. I work in a company that consists of several development teams, all of which have different processes. Some of the teams leverage test cases, some do not. I've noticed that the turn around time it takes for me to pick up a ticket, QA it, and then pass/fail/send feedback is much faster when there is a test case created as I'm not reading through ticket description/comments to figure out what needs to be QA'd.

Incentivized

• Time saving and productivity enhancement for QA teams by preventing context and tool switching
• High observability to management via QA Dashboards

Incentivized

• Improved test management process and collaboration inside team.
• Increased transparency of QA work.
• Team became more satisfied.

Incentivized