JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.
$10
per month
Tricentis qTest
Score 5.1 out of 10
N/A
Tricentis qTest (formerly QASymphony) provides enterprise-level agile testing tools giving businesses visibility and control needed to ensure application quality in fast-paced development environments. Tricentis and QASymphony merged in summer 2018.
The main tool we compared to Tricentis qTest Explorer was the "Steps Recorder" that comes with Windows. We selected Tricentis qTest Explorer because, at least at the time, Steps Recorder would sometimes skip recording arbitrary steps, which didn't meet our needs.
Quality Assurance Manager - Application Development & Support
Chose Tricentis qTest
None of our previous tools we listed in the available drop-down options. We had previously used Spira Test and Xray as our test repositories. We are currently evaluating Test Rail, Zephyr, PractiTest, and others.
From an organizational perspective, qTest is better than Xray as …
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.
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
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.
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.
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.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.
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.
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