Jama Analyze (Discontinued) vs. Tricentis qTest

The integration with JIRA is quite a handy tool to have. It allows for team progress to be easily tracked and visualized using the software while key metrics are brought to the forefront through the software's business intelligence. It makes presenting data and milestones achieved to non-technical management quite simple and can be extremely useful.

Incentivized

I've only used the Tricentis qTest Explorer portion of Tricentis qTest (I recall some of the test management stuff being too clunky and prescribed to fit our workflow, so we chose a different tool). It's well suited for automatically capturing screenshots of browser-based or Windows-based applications during test sessions. However, we've had difficulty getting it to work well in other contexts, such as inside a Virtual Machine or on Linux.

Incentivized

• This allows us to keep track of our team's work by integrating with our product boards on JIRA.
• It allows us to create visualized reports for our team's progress.
• It allows us to gain insights about things that are going well in our product pipeline as well as potential areas of concern based on the data that is collected.

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

• The service tends to be slow at times and working offline can be a pain.
• It has a bit of a learning curve when you start out.
• The price is quite high for the features it offers.

Incentivized

• 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.

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

Jama Analyze, as well as Asana, connect with JIRA to visualize milestone tracking and team progress. While Asana is cheaper, Jama Analyze provides better reports and visual data. Google Data Studio, through a bit of tinkering from your software development team, can achieve similar results, however, the charts and graphs leave a bit to be desired in terms of design. In all, Jama Analyze is great if you have few users and don't need to go for the licensing option. Otherwise, there are definitely cheaper options available but you may have to sacrifice on performance and look-and-feel.

Incentivized

We felt like for the feature set and due to the fact it was mid-range on the cost, it was a good choice. It also has some other plugins which we plan to utilize at some point like Tosca.

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