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

Atlassian Confluence vs OpenText ALM / Quality Center comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

ROI

Sentiment score
7.4
Confluence improves knowledge sharing, reduces onboarding time, and offers cost-effective benefits with a risk-free trial for up to ten users.
Sentiment score
6.8
OpenText ALM enhances oversight, testing efficiency, and collaboration, offering cost savings and reduced defects, despite standardization challenges.
It acts as an enabler for effective test and program management.
 

Customer Service

Sentiment score
6.6
Atlassian Confluence's customer service is generally helpful, but experiences vary, with some users opting for premium or internal support.
Sentiment score
6.2
OpenText ALM customer service varies from fair to excellent, but response times and expertise often need improvement.
This team manages all queries and uses various plugins, such as Tempo for time tracking.
Technical support has been excellent.
Quality is always high yet not perfect.
 

Scalability Issues

Sentiment score
7.3
Atlassian Confluence is highly scalable, efficiently supporting diverse environments and large enterprises despite Data Center version cost concerns.
Sentiment score
7.3
OpenText ALM/Quality Center excels in scalability and flexibility, despite some licensing and performance challenges, meeting diverse organizational needs.
 

Stability Issues

Sentiment score
7.9
Atlassian Confluence is generally stable and reliable, with minor slowdowns resolved through infrastructure improvements and automatic data saving.
Sentiment score
7.2
OpenText ALM/Quality Center is generally stable and dependable, though it faces occasional performance and crash issues under heavy use.
From a stability standpoint, OpenText ALM Quality Center has been pretty good.
 

Room For Improvement

Atlassian Confluence needs enhancements in usability, collaboration, integration, and administrative features for improved efficiency and user-friendliness.
OpenText ALM/Quality Center struggles with high costs, outdated features, poor integration, inadequate reporting, and limited modern methodology support.
The software does not currently have any kind of AI integration.
This chart used AI to offer users the option to create it based on the data.
Improvements are needed so that the system can continue running without creating a new run.
HPLM has one of the best UIs compared to other test management tools, allowing for efficient navigation between test pieces, test folders, test suites, and test execution.
I see a stable tool that remains relevant in the market.
 

Setup Cost

Atlassian Confluence is budget-friendly but add-ons and user expansion can significantly increase costs over time.
OpenText ALM/Quality Center pricing is high, justified for large enterprises, but users seek more competitive pricing versus open-source rivals.
It streamlines license management and renewal processes, which can otherwise lead to complications or lapses in access.
It would be cheaper to use a cloud model with a pay-per-use licensing model.
 

Valuable Features

Atlassian Confluence enhances collaboration and document management with seamless JIRA integration, real-time editing, and extensive customization options.
OpenText ALM/Quality Center offers robust traceability, customization, tool integration, test management, automation support, and comprehensive reporting for effective project tracking.
It's accessible from anywhere, and people from different regions, like India or Germany, can use it in their own time zones.
The integration with internal applications and CollabNet is made possible through exposed APIs, allowing necessary integrations.
It creates constant visibility into the test process, showing the status, bugs, and automated test results.
We can create a requirement for stability metrics with the test cases to ensure all requirements are covered.
 

Categories and Ranking

Atlassian Confluence
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
105
Ranking in other categories
Corporate Portals (Enterprise Information Portals) (2nd), Enterprise Social Software (2nd), Knowledge Management Software (1st)
OpenText ALM / Quality Center
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
207
Ranking in other categories
Application Lifecycle Management (ALM) Suites (5th), Test Management Tools (1st)
 

Mindshare comparison

Atlassian Confluence and OpenText ALM / Quality Center aren’t in the same category and serve different purposes. Atlassian Confluence is designed for Corporate Portals (Enterprise Information Portals) and holds a mindshare of 16.1%, down 19.4% compared to last year.
OpenText ALM / Quality Center, on the other hand, focuses on Application Lifecycle Management (ALM) Suites, holds 5.6% mindshare, up 5.4% since last year.
Corporate Portals (Enterprise Information Portals)
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Massimo Banzi - PeerSpot reviewer
Flexible, efficient, allows the concurrent development of documentation and lets you add comments offline
An area for improvement in Atlassian Confluence is encouraging more vital interaction among the project members or users involved. I was researching a tool, but I forgot the exact name of the tool, and that tool could be used for better interactions offline among users on a specific topic, development, or discussion. I want that feature to be present in Atlassian Confluence. If there's a possibility to integrate Atlassian Confluence, Jira, and that other tool, that will make Atlassian Confluence better. My team had problems accessing Atlassian Confluence a couple of times, but I wonder if that was due to a network, server, or tool issue. I have to say that I've been working with Atlassian Confluence for years, and it has been improving its functionalities, so I feel that as a tool, it's working very well, but some features could still be improved. For example, the search engine should allow you to define some keywords you could use when searching, though I wonder if it's staff-related or setup-related, or lacking in the search engine function itself. I also want artificial intelligence added to Atlassian Confluence where you're working on a specific issue or argument, and Atlassian Confluence, through its AI, can propose some improvements based on what has been done on the same topic by different teams or different projects within the same infrastructure, similar to an internal reference, which can be helpful. Through AI, it would also be great if Atlassian Confluence could advise you on what has been done outside your specific project, and maybe there's the possibility of an installation where you have several projects installed and working together. Another feature that would be good to have in the next release of Atlassian Confluence is the tool recognizing a keyword or two that's fully developed in project B, which you can use in project A, for example.
Paul Grossman - PeerSpot reviewer
Range of supported technology expands, but odd IDE design still leave newbies and pro users alike disappointed.
There are always new features and more support for new and legacy technology architectures with each release. But the bad news is a growing list of long-standing issues with the product rarely gets addressed. While I have a larger list of issues that make day to day work harder than it needs to be, these are the Top Five that I do wish would capture someone's attention in upcoming releases. All hit the tool's ROI pretty hard. #1) Jump To Source - The Silent Code Killer: In older QTP versions a double-click on any function in the Toolbox window would take the developer to the function's source code, while a drag from the Toolbox would add it to the code window. Since 12.0 a double-click on a function in UFT's Toolbox window now ADDS the function (same as drag) to the Code window - to whatever random location the cursor happens to be at - even if it is off screen, and it will replace sections of code if it is highlighted. We are not sure what the intention was, but our Best Practice is to avoid the Toolbox window entirely to avoid the real danger of losing days of work and needless bug hunts. Now Jump to Source is not all bad. A right-click on any function called from a Script takes us to the code source, which is great! But it only half works: in a Library, only for functions declared within the same library. Our advance designs have well over twelve libs so a whole lot of extra time is spent searching the entire project for a function's source on a daily basis. Lastly, while we can add custom methods to object, a Jump To Source from these methods is long overdue. So again our only option is to search the entire project. #2) Object Spy: It needs to have multiple instances so that you can compare multiple object properties side-by-side. It lacks a Refresh button, so that automation engineers can quickly identify the property changes of visible and invisible objects. Or HP could skip to option #3... #3) Add RegEx integer support for .Height or .Width object properties when retrieving object collections. If this were possible, our framework could return collections that contain only visible objects that have a .height property greater that zero. (Side Note: the .Visible property has not returned a False value for us in nearly five years - a recent developer decision, not a product issue) Eliminating the need to separate the non-visible objects from visible ones would decrease execution time dramatically. (Another side note: Our experiments to RegEx integer-based .Height properties found that we could get a collection of just invisible objects. Exactly the opposite of what we needed.) #4) The shortcut to a treasure trove of sample code in the latest release 14.0 has been inexplicably removed. This impeeds new users from having an easy time learning the tool's advanced capability. In fact the only users daring enough to go find it now will be you who is reading this review. #5) Forced Return to Script Code. This again is a no-brainer design flaw. Let's say we run a script and throw an error somewhere deep in our function library. Hey it happens. In prior QTP versions when the Stop button would be clicked the tool would leave you right there at the point where the error occurred to fix. Now in recent releases, UFT always takes us back to the main Script, far from that code area that needed immediate attention.
report
Use our free recommendation engine to learn which Corporate Portals (Enterprise Information Portals) solutions are best for your needs.
832,138 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
74%
Financial Services Firm
4%
Computer Software Company
4%
Manufacturing Company
3%
Educational Organization
65%
Financial Services Firm
7%
Manufacturing Company
5%
Computer Software Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Atlassian Confluence?
The most valuable feature of the solution stems from its document-controlling feature. In Atlassian Confluence, controlled documents cannot be edited by anyone else.
What is your experience regarding pricing and costs for Atlassian Confluence?
Atlassian products, including Confluence, have yearly price increases of approximately five to twenty percent.
What needs improvement with Atlassian Confluence?
There is a significant difference between the data center version and the cloud version of Confluence. Providing the same features in both versions would be beneficial. Additionally, there is no fu...
What do you like most about Micro Focus ALM Quality Center?
The most valuable feature is the ST Add-In. It's a Microsoft add-in that makes it much easier to upload test cases into Quality Center.
What is your experience regarding pricing and costs for Micro Focus ALM Quality Center?
The on-premises setup tends to be on the expensive side. It would be cheaper to use a cloud model with a pay-per-use licensing model.
What needs improvement with Micro Focus ALM Quality Center?
The extract format is not ideal, splitting expected results into three line items, making interpretation difficult. Issues with mapping multiple functional test cases to one automated test case nee...
 

Also Known As

Confluence
Micro Focus ALM Quality Center, HPE ALM, Quality Center, Quality Center, Micro Focus ALM
 

Overview

 

Sample Customers

Facebook, Skype, Microsoft, NASA, Netflix, Adobe, Bonobos, LinkedIn, Pfizer, Citi.
Airbus Defense and Space, Vodafone, JTI, Xellia, and Banco de Creìdito e Inversiones (Bci)
Find out what your peers are saying about Microsoft, Atlassian, Liferay and others in Corporate Portals (Enterprise Information Portals). Updated: January 2025.
832,138 professionals have used our research since 2012.