We performed a comparison between Codebeamer and OpenText ALM Octane based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is a stable solution."
"One of the most valuable features of Codebeamer is its strong performance."
"The solution easily replaces IBM DOORS, which no longer offers maintenance in China."
"You can track the metrics in the Agile dashboard very easily."
"The platform provided the flexibility to expand our business processes, accommodating or altering them to suit the requirements of a changing environment."
"Codebeamer's API-based integration and many other integration aspects with other solutions are very powerful."
"CodeBeamer provides full traceability, excellent collaboration, regulatory compliance, and instant reporting with its holistic approach from requirement management to testing."
"The traceability is so simple that I don't need to do any additional configurations related to traceability."
"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."
"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."
"A valuable feature is the pipeline, so that we can now connect to Jenkins and then have all the results from testing, from external, in the tool, so that we can see the whole approach from there. Also, We can work with labels so we have better filtering solutions than in ALM. And it's much smarter and leaner to use than ALM."
"We are seeing some real improvements in the way we do things. We are becoming more agile in the way we do it because of that and in a way that stories are managed. Stories are given lifecycles as opposed to just being entities within a tool."
"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 most valuable features of the solution are its ability to manage test scenarios, test results, and test automation, which are its primary functionalities."
"It’s easy to set up."
"We looked at all the market-leading tools, but we did not find anything quite as comprehensive as ALM Octane. When I say comprehensive, it's not just a single tool for Agile planning, backlog management release, sprint planning, etc., but it also has a built-in, comprehensive quality management module. It also has pipelines where we can hook up with our DevOps ecosystem/toolchain."
"We would like to see more industry-specific features that are tailored to the vertical markets."
"It's still a fairly new tool that lacks maturity right now."
"The solution has a very small market share in China. It's almost like a startup."
"During migrations from other platforms to CodeBeamer, there have been instances where we encountered issues that required redoing certain tasks."
"Usability needs to be improved."
"It would be helpful if Codebeamer's overall processing and integration with software like Jira could be improved."
"I would like to see more, easily trackable reports."
"Certain areas in Codebeamer could be improved, like addressing small issues, glitches, or bugs."
"The product's requirements management feature needs enhancement in terms of functionality."
"I have yet to experience the CI/CD part of Micro Focus ALM Octane but as demonstrated by the team who is providing the services, I see that the CI/CD could improve. When we check in the code, for the code snippet that has been checked in by a particular user, you need to open a separate file. When comparing Micro Focus ALM Octane to Jira, they have a separate window in which you can click on the ID and the code is visible in the snippet. It's a two-step process in Micro Focus ALM Octane and it's a single-step process in Jira. It's essential for the developers to think about this difference."
"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."
"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"
"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."
"The reporting is lacking from a requirements matrix and a traceability perspective."
"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."
"It could use just some small improvements. I would like additional features, like planning features, user story mapping, or connection to collaboration tools."
Codebeamer is ranked 9th in Application Lifecycle Management (ALM) Suites with 10 reviews while OpenText ALM Octane is ranked 5th in Application Lifecycle Management (ALM) Suites with 38 reviews. Codebeamer is rated 7.8, while OpenText ALM Octane is rated 8.2. The top reviewer of Codebeamer writes "Has good technical support services, but the migration process needs improvement". On the other hand, 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". Codebeamer is most compared with PTC Integrity, Polarion ALM, Microsoft Azure DevOps, Jira and OpenText ALM / Quality Center, whereas OpenText ALM Octane is most compared with Jira, OpenText ALM / Quality Center, Microsoft Azure DevOps, Rally Software and ServiceNow Strategic Portfolio Management. See our Codebeamer 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.