Tricentis qTest: a powerful tool if you know what you're doing
June 11, 2022
Tricentis qTest: a powerful tool if you know what you're doing
Score 4 out of 10
Vetted Review
Verified User
Overall Satisfaction with Tricentis qTest
Our organization used Tricentis qTest to document automated and manual test cases. Tricentis qTest was the first dedicated tool we've ever used to document test cases, and it was sorely needed because there was no single repository/source for our applications' use cases. Having a dedicated tool for this allowed us to organize and crowd-source our tests, and it made the reuse of tests significantly easier and cleaner.
- 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.
- Tricentis qTest wasn't particularly easy to use, especially for an organization that had not previously used to test case management tools. While there were a lot of things that you could do, the complexity made it difficult to just get started.
- Not necessarily a comment about the tool itself, but the support that we got (or rather didn't get) from Tricentis left a lot to be desired. We were left to figure out a lot of things on our own. Training and product documentation was also lackluster.
- The dedicated licenses were very expensive for a fledgling QA team. This prevented us from having enough licenses for everyone on the agile team to work with test cases. This was particularly painful because the full "read-write" license was required for anyone to just view test cases, a point that Tricentis sales staff misled us on.
- The connectivity with Jira was temperamental and took an insane amount of time to set up the end to get working reliably. Support didn't work U.S. hours, requiring us to sync with them during early morning hours.
- Because of the challenges that we had started to use and the sheer cost of the licenses, this tool has had a negative impact on our ROI.
- The quality team had a hard time learning to use the tool and full adoption didn't take place. We eventually decided on a more user-friendly tool that the team has very successfully adopted.
- Jira
We did Tricentis qTest requirements integration with Jira. Initially, things looked like they were going to be simple to set up, but there were numerous problems throughout that led to it taking 3 months (including lackluster support from Tricentis qTest) to get things working semi-reliably. The defects integration with Jira was far simpler and that was set up in hardly any time at all.
Because of the challenges we experienced set up the tool, we weren't able to use the tool extensively enough to get an accurate feel for this. Even before we were fully established with the tool, we were regularly receiving emails from Tricentis qTest (incl. directly from our relationship manager) to add their Tosca tool as an extension to Tricentis qTest, so the claim that Tricentis qTest should provide a view of all your software testing activities feels misleading.
Do you think Tricentis qTest delivers good value for the price?
No
Are you happy with Tricentis qTest's feature set?
Yes
Did Tricentis qTest live up to sales and marketing promises?
No
Did implementation of Tricentis qTest go as expected?
No
Would you buy Tricentis qTest again?
No