Try our new research platform with insights from 80,000+ expert users

OpenText Software Delivery Management vs PractiTest comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 19, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

OpenText Software Delivery ...
Ranking in Application Lifecycle Management (ALM) Suites
7th
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
41
Ranking in other categories
Enterprise Agile Planning Tools (7th)
PractiTest
Ranking in Application Lifecycle Management (ALM) Suites
21st
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Test Management Tools (18th)
 

Mindshare comparison

As of June 2025, in the Application Lifecycle Management (ALM) Suites category, the mindshare of OpenText Software Delivery Management is 6.0%, up from 5.5% compared to the previous year. The mindshare of PractiTest is 0.4%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

GeorgNauerz - PeerSpot reviewer
A stable tool for sprint planning, test management, quality management, and automated testing
I think the area of release management in the tool is an area of concern where improvements are required. In general, the connection between releases and scrum teams needs improvement, as it could be optimized owing to its linkages, making it very uncomfortable as soon as you have strong teams or scrum teams that work with different items over several releases. In future product releases, the solution needs to focus a bit more on the metric part. The product's dashboard is a metric for productivity and process control.
DC
Flexible and intuitive with easy reporting, and good support that is instantly available through chat
It doesn't allow you to connect to multiple different bug tracking tools at the same time. This is not an issue if you only have one bug tracker but we can potentially use different tools for different projects. As an example, if you connect PractiTest to Jira for one project, that's the one you have to use for all projects. We had a requirement to connect with Jira for one project, and a different tool for another, project but it was unable to accommodate that unfortunately. I would therefore like to see it easier to integrate with bug tracking tools at project level which would give each project the opportunity to use a different bug tracker if required.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The integration capability of ALM Octane was very straightforward. We had a supporting team, and they provided us with detailed documentation."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"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."
"The solution natively supports Agile-Waterfall hybrid software development at an enterprise scale. This is very important to us. Because even though the company wishes to go Agile, we still have projects which follow a Waterfall methodology. In order for us to accommodate both, we needed some sort of hybrid system. Because if we are using a fully Agile system, then the reporting might not be correctly extracted."
"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."
"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."
"Octane works well with the Jira portfolio to track the project with two methods: Agile and Waterfall. We can track all the testing in Waterfall or Agile and synchronize it with Agile tools."
"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."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
 

Cons

"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."
"Documentation is not clear."
"Security and security management, meaning the integration of the security, could be enhanced. We know about Fortify, but it would be better to have security features in the original Octane platform without the need for another solution or another application."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"Promoting it more could help a lot of projects."
"Technical support can be slow."
"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."
"What could be improved in Micro Focus ALM Octane is its integration with Jira."
"It doesn't allow you to connect to multiple different tracking tools."
 

Pricing and Cost Advice

"It will be as expensive as ALM.NET, if not more expensive. But here's a good tip: If you have ALM.NET, you are able to share your licenses from ALM.NET to Octane. You just have to define a dedicated number of licenses on ALM.NET and then you can share them with ALM Octane, with some configuration effort. This is something that you have to take into account, that there is a possibility of such license sharing that could decrease your costs. Compared to open-source tools, the price the ALM Octane is definitely higher, in terms of the licensing cost."
"Pricing is the weakest point. It is expensive, but the tool has plenty of features. The main problem we have is that the pricing is very high compared to some other solutions."
"I rate the tool's pricing an eight on a scale from one to ten, where ten is very expensive."
"I rate the product price an eight on a scale of one to ten, where one is cheap, and ten is expensive. The product is neither cheap nor expensive."
"For what it does, it's very reasonably priced. I like the licensing model as well, because it's very flexible. You can scale licenses up and down for short periods of time."
"If you compare the price with the functionality, it is pretty much the same as other solutions. If you compare it to Jira, for instance, it has a lot more functionality. You don't need any plug-ins, but it's also more expensive. Once you start adding your different plug-ins to Jira, you'll probably end up with the same amount or more. There is also a yearly support cost, which is usually 25% of the initial cost of the license."
"It's pretty pricey, one of the most expensive ones on the market... The value depends on if you use all the features that it has. It comes with a lot of features. The difference between the license structure of ALM and Octane versus JIRA, is that you get everything with ALM and Octane... For JIRA, you buy the pieces one piece at a time."
"Going forward, I think we will want to explore adding more licenses."
"Pricing is probably in the middle, it's not the cheapest but it's not the most expensive."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
858,038 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Manufacturing Company
11%
Computer Software Company
11%
Government
8%
Computer Software Company
24%
Financial Services Firm
21%
Government
6%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Is Jira better or would you go with Micro Focus ALM Octane?
Hi Netanya, Basically , it all depends on the use cases for your environment and the business needs. Hope the below data may be relevant to you for identifying your needs and deciding on the approp...
What do you like most about Micro Focus ALM Octane?
The platform's most valuable feature is pipeline integration or continuous integration services.
What is your experience regarding pricing and costs for Micro Focus ALM Octane?
OpenText ALM Octane is an expensive product. However, it offsets costs by saving time and money, thus creating a balance between expenses and benefits. Our organization with over 1500 users sees sa...
Ask a question
Earn 20 points
 

Also Known As

Micro Focus ALM Octane, Micro Focus Octane
No data available
 

Overview

 

Sample Customers

Orange, Airbus, Haufe Group, Kellogg's, Claro, Bon Secours, World Wide Technology
Canonical, SAS, Amobee, Play Buzz, Abbott, Aternity, Zerto, Freeman
Find out what your peers are saying about OpenText Software Delivery Management vs. PractiTest and other solutions. Updated: June 2025.
858,038 professionals have used our research since 2012.