Overall Satisfaction with Tricentis qTest
We use qTest for our test cases and requirements repository, as well as tracking test cases execution status. The business problems qTest addresses for us is having traceability of feature requirements to test cases creation, manual test execution and automation status. Also ability to assign test cases to individual testers, create test plans for different releases, and run reports on them. Having the ability to integrate with Jira was crucial to support our SDLC. Most of the application teams within SAP Ariba is using qTest for the above purposes.
- Ease of integration with Jira
- Ability to customize test case properties
- Easy to organize and create test plans and having visibility to statistics and execution summary.
- Data query is slow for large projects (64109 test cases). It's not usable because the screen won't even load.
- It would be nice to be able to add user to groups directly within the individual user Action menu. Instead of having to create user, assign projects, then go to Groups to add the user.
- Some simple filtering with the search function or make it context based. So that if I am in Test Design tab, and I run a search, provide results for TC's only. Right now it returns everything from Requirements and Test Runs, etc.
- Better test cases format standardization across teams.
- Better test plan standardization.
- Faster development and testing, especially when a hot fix is needed. The ease of creating a test plan from scratch helps.
Insights is a great tool to create customized reports to tack testing activities.
Prior to qTest, the teams were using TestLink.
Do you think Tricentis qTest delivers good value for the price?
Not sure
Are you happy with Tricentis qTest's feature set?
Yes
Did Tricentis qTest live up to sales and marketing promises?
Yes
Did implementation of Tricentis qTest go as expected?
Yes
Would you buy Tricentis qTest again?
Yes