We performed a comparison between Micro Focus ALM Octane and Micro Focus ALM Quality Center based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Micro Focus ALM Octane ultimately won out in this comparison. According to reviews, Octane appears to be a more comprehensive and high performing solution.
"Its end-to-end traceability is one of the big advantages. Most of our agile projects work in a closed team structure. We are seeing what is the flow, where we are, and what is the project milestone. So, it provides end-to-end traceability and good visibility of project milestones."
"With an Octane project, we have our automation, our requirements, our tests, our pipeline into build-and-deploy, and the ability to identify problem areas. It makes things quicker because it's more along the lines of an automated process."
"Backlog management is the most valuable feature. This was a capability that was missing or difficult to achieve in ALM Quality Center."
"The key feature is the usability. It is fast to learn and easy to use. It's very intuitive to work with. Most of the important functions are available via a few clicks, compared to other tools where I have to open a sub-menu and then a sub-menu and another sub-menu, and then press a button."
"The most valuable feature of Micro Focus ALM Octane is the reports. We are able to do customization."
"It's more streamlined because we have it all under one umbrella. And once the business requirements and rules have been created, we can do test cases and apply them to the business rules."
"On the user side, what I like a lot is the reporting capabilities. There's no tool, to my knowledge, that gets anywhere close to Octane at the moment when it comes to the reporting capabilities. I can do everything with the reporting. There's nothing missing. I have all the options. I can create graphs, including graphs of several types and looks."
"The most useful feature of Micro Focus ALM Octane is the dashboards, they are easy to use."
"With test execution, you have an option to create custom fields. It is also really user-friendly. With other tools, we only have restricted fields and we cannot customize or add new columns or fields that users can make use of while testing. ALM is very flexible for creating new fields. It is easy for users to understand the application."
"This solution is open and very easy to integrate. The interface is good too."
"It's user friendly, scalable, and very stable and strong. It's cooperative, meaning that I can assess the test to check it and follow the flow of defects, and the developers and the business can use this tool to follow the test process."
"It has a good response time."
"By standardizing our template, we publish reports at the business unit level."
"ALM Quality Center is a reliable, consolidated product."
"Cross project customization through template really helps to maintain standards with respect to fields, workflows throughout the available projects."
"The setup is pretty straightforward."
"The limitation of Octane is that we can't do a release outside of the sprint. We can only plan the release in the sprint. With Agile and JIRA tools, we can plan the release outside the sprint and do a global release of all the projects from the sprint."
"We’d like to see Platform One/Iron Bank compliant containers."
"The solution should improve by adding scrum board-like functionality."
"Also, while there is a Requirements Module in Octane, it is very plain. It's okay to have some requirements described there, but it's not really following the whole BDD approach. I would like to have more features for requirements in there."
"There's a trend in our requests to have the ability to export data, en masse, out of Octane. There are capabilities within Octane to export data, but there are specifics around test suites and requirements and relations, as well as certain attributes, that we would like to be able to export easily out of Octane and into a database or Excel."
"The product's requirements management feature needs enhancement in terms of functionality."
"Because JIRA is a leading tool for both development and requirements management - everybody is using JIRA - I'm pretty there will be a use case where people are trying to connect between ALM Octane and JIRA. The back-end configuration of the synchronization with JIRA could be simplified. The architecture is really complicated. We required a lot of machines to build the cluster and the configuration was not really clearly described within the documentation. This may have something to do with the fact that the software is pretty new."
"Globally, I don't see many major points of improvement. It's mostly plenty of little things, and it's weird to me that they are not in the product yet. They are really details, but they're annoying details... Today, in the tool, we've got plenty of assets we can handle, like requirements, user storage, defects, tasks and so on. And to all of those elements, we can add comments. We can add comments to any asset in Octane but not to tasks. It's just impossible to understand why it's not available for the tasks because it's available everywhere else. Similarly, for attachments, you can attach files absolutely everywhere except on automated runs, which is, again, awkward. I don't understand why on this element, in particular, you cannot do it. It's little touches like that."
"The BPT also known as Business Process Testing can sometimes be very time intensive and sometimes might not be very intuitive to someone who is not familiar with BPT."
"Is not very user-friendly."
"Micro Focus ALM Quality Center should improve the reports. Reporting on tax execution progress against the plan. However, they might have improved over two years since I have used the solution."
"The version of Micro Focus ALM that we use only works through Internet Explorer (IE). We have to communicate to everyone that they can only use IE with the solution. This is a big limitation. We should be free to use any type of browser or operating system. We have customers and partners who are unable to log into the system and enter their defects because they work on a different operating system."
"There is room for improvement in the scalability and stability of the solution."
"Defect ageing reports need to be included as built-in."
"We have had a poor experience with customer service and support."
"ALM requires that you install client side components. If your organization does not allow admin rights on your local machine, this means you will need someone to run the installation for you with admin rights. This client side install is also limited to Internet Explorer and does not support any other browsers."
More OpenText ALM / Quality Center Pricing and Cost Advice →
OpenText ALM Octane is ranked 5th in Application Lifecycle Management (ALM) Suites with 13 reviews while OpenText ALM / Quality Center is ranked 6th in Application Lifecycle Management (ALM) Suites with 17 reviews. OpenText ALM Octane is rated 8.2, while OpenText ALM / Quality Center is rated 8.0. The top reviewer of OpenText ALM Octane writes "A stable solution used for test management that is perceived to be an outdated tool by its customers". On the other hand, the top reviewer of OpenText ALM / Quality Center writes "It is a stable solution, and customer service is its most valuable feature". OpenText ALM Octane is most compared with Jira, Microsoft Azure DevOps, Rally Software, GitLab and Codebeamer, whereas OpenText ALM / Quality Center is most compared with Microsoft Azure DevOps, Jira, Tricentis qTest, Zephyr Enterprise and Tricentis Tosca. See our OpenText ALM / Quality Center vs. OpenText ALM Octane report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.