Micro Focus ALM Octane Pros and Cons
Micro Focus ALM Octane Pros
The concept of Octane is to have the most information and the most important functions available with one or two clicks. This is a big point of savings, in time and money... The powerful widgets, the Dashboard module, the ability to drill down to the information you need and the ability to configure it to your needs, are big advantages.
The general capabilities of Octane, setting up rules instead of programming VBA scripts for controlling the workflow, and making life easier for the users with the template functionalities, are very big benefits.
The openness and the possibilities of the REST API, from an operations and maintenance perspective, are a big plus.View full review »
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.
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.View full review »
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.View full review »
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.View full review »
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.View full review »
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.View full review »
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.View full review »
The most important feature is the integration among all the different features in just one tool: Agile management system, requirements management system, test management, defects management, automatic test execution. Really, if you're looking at other tools, you will never find all that integrated into just one tool with all the traceability, with all the elements in just one place.View full review »
Backlog management is the most valuable feature. This was a capability that was missing or difficult to achieve in ALM Quality Center.View full review »
Octane creates a gentle approach to Agile-based projects.View full review »
Micro Focus ALM Octane Cons
An example of one of the features we have requested is inheriting information from a test suite into a suite run and into a menu run, so the user does not have to add that information, update it manually.View full review »
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.
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.View full review »
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.View full review »
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 solutionView full review »
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.
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.View full review »
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.View full review »
There is an opportunity for them to do a little more with the dashboarding. We still feel that HPE Quality Center/HPE ALM reporting is very powerful. We talked with R&D, and there are some things on their roadmap, but at the same time, their strategy is to connect Octane with visualization tools such as Power BI.View full review »
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.View full review »
Octane, from an administration perspective, is very limited. The application is improving with each release but what is missing is the ability to manage users and workspaces. I would also like "usable" reporting for more than a few workspaces. Also still missing is the ability to copy a workspace or get data in or out, except for limited REST calls.View full review »
Improvements could be made by way of additional integrations across the lifecycle.View full review »