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

Well suited - where you have a set of cases defined say for regression and then you can mark them as Pass/Fail/Skipped, etc. If you wish to present the impact of certain set of new features, bug fixes,etc, you can use this tool Not well suited- where the user is naive and don’t have much understanding of test reporting tools as this tool is slightly difficult to learn at a glance

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

• UI has a lot scope of improvement
• Uploading of test screenshots and managing them can be more effective
• User experience can be improved
• Tracking of tests can be more simplified

Incentivized

As I am a tester, for me I found this tool to be new in terms of everything like the management of tests, plans, releases, reporting,etc. It is overall a good tool for test reporting and can be used for reference in the future. I liked several features of on the go placement of screenshots. Also I feel like the UI , the font, the color combination can be improved

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

• We are able to easily pull reports any time management would like to see them
• Jira integration makes it easy to attach to stories/defects and save time
• A quick overview at the system's health as a whole is easy to see from TestRail

Incentivized