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.
"The platform's most valuable feature is pipeline integration or continuous integration services."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"There are a lot of predefined reports. We can attach additional reports for users, like who worked on what defect and when, as well as what is the status of the release compared to the previous release. It is really endless. All the data is really linked together. Then, if all the data is linked together, there is an option to prepare reports out of it. We are very impressed with its reporting capabilities."
"The defect management gives us full-fledged capabilities for handling defects, including capturing the details of the defects and even screenshotting the defect cases. The defect management is comprehensive."
"The user experience is a lot better than any tool that I have used before. Overall, it is great. It has a smooth interface, which is very user-friendly. It makes it easier to work together and have more transparency and customization, which is very good."
"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."
"The integration points are very good. Octane gives us a window not only into our manual testing, but also our automation testing and our performance testing. We can see all results from all three streams of testing in one place."
"It is a very stable solution. Stability-wise, I rate the solution a ten out of ten."
"The most valuable user feature that we use right now is the camera."
"Being able to manage tests as this is something very difficult to find in other products."
"The product can scale."
"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."
"The test-case repository and linkage through to regression requirements will absolutely be a key component for us. We haven't got it yet, but when we've got an enterprise regression suite, that will be a key deliverable for them. We will be able to have all of the regression suite in one place, linked to the right requirements."
"The solution is very user-friendly."
"The execution module and the test planning module are definitely the most valuable features. The rest we use for traceability, but those are the two modules that I cannot live without."
"Having the links maintained within the tool is a huge boon to reporting requirements, tests, and defects."
"When I manage projects that are being created in ALM, I have a standard template, but I don't have a template for them in Octane. I literally have to create the project from the ground up every time, which for an administrator, is a nightmare solution"
"Documentation is not clear."
"The product's requirements management feature needs enhancement in terms of functionality."
"The reporting is lacking from a requirements matrix and a traceability perspective."
"We have some requests to beef up the manual testing abilities and the ability to report on testing progress. All the basics are there, but there's an issue of maintainability. For example... once you plan a test and it creates a run, more particularly a suite run, you can't edit the suite run afterward... That that is not realistic with how people work. Mistakes are made and people are humans and we change our minds about things. So the tool needs to allow for a bit more flexibility in that testing area, as well as some better widgets to report on progress."
"I think the area of release management in the tool is an area of concern where improvements are required."
"I would like to see the mobile testing improved so that we can simply select a mobile device, then specify what parameters we want, and the testing will be run based on that."
"The Requirements Module could be better, to build up a better requirements process. There's a huge improvement from ALM.NET to Octane, but it's still not really facilitating all the needs of the product owners, to set up their requirements in Octane."
"Quality Center's ability to connect all the different projects to reflect status and progress is quite complicated. We may develop something because there are so many projects. Right now, I have to do something which Quality Center is really not designed for: over reporting. This is a very big problem right now. We may develop some controls, but it is problem at the moment. I love Quality Center for individual projects to work with it. However, if you have a lot of projects for Quality Manager to do cross reporting on many projects, then it's almost impossible. It takes a lot of time."
"It is pricey."
"There is room for improvement in the scalability and stability of the solution."
"There were multiple modules and stuff to the solution so maybe the requirements can map to test scripts. It can't map to test steps. If you've got a process that's set up and you've got multiple test scripts that are in it, each script has to be linked to the requirement and the whole set can't be. If we're doing process-driven testing, it's more difficult to do it at the script level, which is what we're finding from a traceability perspective."
"Certain features are lousy. Those features can drag the whole server down. There are times that the complex SQL queries are not easy to do within this solution."
"Is not very user-friendly."
"I'm looking at more towards something more from a DevOps perspective. For example, how to pull the DevOps ecosystem into the Micro Focus ALM."
"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."
More OpenText ALM / Quality Center Pricing and Cost Advice →
OpenText ALM Octane is ranked 7th in Application Lifecycle Management (ALM) Suites with 38 reviews while OpenText ALM / Quality Center is ranked 5th in Application Lifecycle Management (ALM) Suites with 197 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 "Reporting engine, widgets, and dashboards are a huge plus, and powerful REST interface means we can interact with other tools". On the other hand, the top reviewer of OpenText ALM / Quality Center writes "Offers features for higher-end traceability and integration with different tools but lacks in scalability ". 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 OpenText UFT One. 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.