Zephyr Enterprise vs. Tricentis qTest

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 qTest is well-suited for organizations transitioning to Agile or DevOps frameworks. It Streamlines test management with real-time collaboration and integrates with popular CI/CD tools. It excels in complex, large-scale projects needing centralized test cases management, traceability, and detailed reporting. However, organizations on a tight budget might find it cost prohibitive compared to simpler, low-cost alternatives.

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

• Highly customizable: we were able to organize our test cases in unique ways that made our work easier.
• Connectivity with Jira: being able to pull requirements information in from Jira was a big point for us.
• Standalone tool: Being a standalone tool on a dedicated server, we were able to have access to our tests regardless of whether our Jira server was down.

Incentivized

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

Incentivized

• In requirements , we can't add multiple test cases at once, or search multiple cases at once, need to do one by one. Here actually qtest needs to improve.
• Linking cloud hosted qtest and on-premise TOSCA is very difficult especially when you are working with client system with security wall. It requires tunnelling software which is not recommended.

Incentivized

This has been a core QA management tool for our organization and integrates well with our other SDLC platforms (Azure DevOps/Jira/Katalon).

Incentivized

qTest is actually intuitive and user-friendly, despite my other scathing review aspects

Incentivized

The actual answer is 0. I have never experienced worse support, whether personal or professional

Incentivized

Again, supporting documentation could have been a lot better

Incentivized

Incentivized

Extensive integration options with various third-party tools, enabling seamless integration into existing workflows. Allows for flexibility and customization of workflows, fields, and permissions to adapt to unique testing requirements. Supports robust requirements traceability, ensuring comprehensive test coverage. Lastly management decisions too

Incentivized

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

Incentivized

• Better organization and centralization of test cases has led to more cohesive team collaboration
• Speed to delivery, deployments to production, are mostly maintained
• Performance issues have led to testing delays requiring the team to switch to other methods which contributed to QA bottleneck issues and sometimes even missed sprint commitments

Incentivized