We performed a comparison between Inflectra SpiraTest, Jira, and OpenText ALM Octane based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, Microsoft, IDERA and others in Test Management Tools.
"The ability to reuse test cases already used across projects is the most valuable feature of this solution. We don't need to create new ones."
"The user-friendly features are the most valuable. For example, migration of requirements and migration of test cases and the creation of traceability. You have various reports that you need. The plug-ins that are available to connect with the other tools."
"I found Inflectra SpiraTest intuitive enough. It's also easy to learn, so this is what I like about it."
"The features of this product most valuable to me were the test case management and the visual status, by which it was displayed."
"Inflectra SpiraTest has a lot of functionality, which is good."
"We were able to add a step-by-step procedure for someone to follow to assist in testing."
"The reporting functionality helps vendors and technical resources identify bugs and issues that need to be addressed. The simple dashboard-style home page makes training end-user testers simple and straightforward. The actual testing UI is VERY straightforward and very intuitive for the end-users that test the system since very often we pull from business and operational users to help test new systems."
"We have around 2000 plus users, so scale wise, there are no issues. We can easily scale up with multiple users."
"The sprint tracking is really helpful and very convenient."
"Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product."
"One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily."
"The solution is very scalable and flexible."
"It is a good defect tracking tool. It has a lot of capabilities and functionalities. There are a lot of graphs and a lot of tracking. It can be sprint-driven if you want."
"Kanban board: The board is easy to use and visually impressive to non-IT users, who found it easy to relate to."
"Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so."
"The platform's most valuable feature is pipeline integration or continuous integration services."
"People really how easy it is to customize. In some previous tools, that has been very limited, or you had to know how to write code to do some of the customizations, or it was very confusing. Going back to the user interface, they've made the customization of the tool, the workspace settings, very easy for people to figure out and use."
"It’s easy to set up."
"The interface is user-friendly."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"The most valuable feature of Micro Focus ALM Octane is the reports. We are able to do customization."
"It's brought our entire team into a single tool. We're all looking at the same real-time data. Our project management office has been able to set up dashboards for individual teams, and do comparisons by teams, of integration, and cross-team integration, burn-up, burn-down, and cumulative flow..."
"The way testing is closely tied into the product Backlog has made it more intuitive, or easier to manage the relationship between building out an application and testing it. In other tools, that is more segregated. The way it's designed in Octane, people have said it makes more sense to them, and that it's easier for them to understand their data and to maintain and test their solutions."
"Two areas that can stand improvement: integration with third party products and making it more intuitive."
"Being able to add scripting for testing can and does save a lot of time. When you are able to just ‘run’ a test case rather than manually add it and run it."
"Migrating is not very easy. It depends on the organization, how efficient and effective the decision-making process is. The plug-ins should be easier and more integrated rather than the user trying to integrate the tools which are more popular, like Jira et al."
"The folder organization in Inflectra SpiraTest could be better, though I cannot comment whether that is structure-related. Most of what I need would probably be in the tool, but as a test manager, I need to be able to create dashboards and reports easily."
"The user interface is slightly complicated and not very consistent. It could be more user friendly."
"It should develop integration with JIRA. We have some complexities which caused us not to decide to integrate it with our JIRA, like synchronous data."
"The UI for managing test cases, test sets, test runs could be a little more integrated, currently, these feel disjointed at times and confusing. Also, the test steps page needs to display the test steps closer to the top of the UI so as to not have to scroll down to find."
"In general, although we use JIRA, we never really learned how to use it properly. The learning curve of the solution is high. It has a lot of power, and yet we don't understand its capabilities."
"The hierarchy for Jira tickets is too flat."
"In Jira Cloud, integration with Excel is missing. Previously, I could import our Excel files into Jira, and I could also download a big Jira report in the Excel format, but now, it needs to be manipulated after that, which is not good. It looks like they've done that on purpose, but I don't understand the reason for it."
"There's a really steep learning curve for configuration."
"One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better."
"The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me."
"The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough."
"There's been the odd amount of JIRA downtime (not self hosted) and sometimes tickets that can't be accessed."
"Technical support can be slow."
"We've only had a few stability issues. Generally, we have issues following any deployment they do, so if they do a deployment on a Sunday, then we may have a couple of issues on a Monday or Tuesday."
"Though Micro Focus ALM Octane doesn't have much of a bug, it lacks integration with some solutions. For example, my company has fairly new software, but it can't be integrated with Micro Focus ALM Octane, so integration with other software, particularly with less popular software, could be improved. Micro Focus ALM Octane also requires a lot of resources during its setup, and I find this another area for improvement. An additional feature I'd like to see in the next release of Micro Focus ALM Octane is the ability to customize the interface, especially when doing a manual test."
"There are some challenges when we want to integrate the tool with other products, and it takes time for a team to figure out how to do it."
"The cluster architecture that we implemented was server to server communication: Octane application to Elasticsearch and Elasticsearch to another Elasticsearch service. Recently, we found this is a security gap. The Octane application is interacting with Elasticsearch server, but that was missing from the requirements and prerequisites in the setup. The Micro Focus team has not given advice on how to implement authentication-based communication between Octane to Elasticsearch, and we found it as a gap later, then our security team asked us to fix that gap. So, there was a lot of time spent on rework."
"The biggest problem with ALM Octane is that it's very complex, so it's difficult to use and scale."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"Updating items, sorting, bulk updates—these things could have a bit more flexibility, but it's still possible to do them."
