OpenText Application Quality Management

Name: OpenText Application Quality Management
Brand: OpenText
Rating: 4.2 (380 reviews)

Leader

Information Reimagined

Est 1991|Valuation $6.8B|Raised $14.3B

LinkedIn 550K|Website|Web traffic 1.1M|FTEs 19,900|HQ Waterloo, Ontario, CA

MarketsInternal Controls & Audit Management Engineering Project Management

OpenText Application Quality Management screenshot

Published Oct 22, 2026

01Common complaints

Organizations that need rapid time-to-value (weeks rather than months) If an organization cannot fund implementation, administration, and process design, AQM’s depth can increase overhead and delay outcomes.
Organizations that are developer-led and operate primarily within Jira If Jira is the primary system of record for delivery, a separate ALM platform can introduce operational friction. Jira-based test management add-ons or Azure DevOps may align better with day-to-day workflows.
Organizations that require full web client feature parity immediately Some reviewers note that the web client transition remains a work in progress and that certain features may be limited. Organizations with strict requirements to avoid client components should validate current web client parity in a hands-on proof of concept.
Price-sensitive organizations or those with small user counts User feedback often highlights licensing costs; smaller organizations can frequently achieve adequate coverage with lower-cost alternatives.
Organizations with complex integration requirements (Jira Cloud, multi-tenant, strict auth) If integration requirements include modern authentication patterns, event-driven integrations, or tight alignment with Jira Cloud, plan for dedicated integration engineering and possible middleware.

1) Organizations that need rapid time-to-value (weeks rather than months) If an organization cannot fund implementation, administration, and process design, AQM’s depth can increase overhead and delay outcomes. 2) Organizations that are developer-led and operate primarily within Jira If Jira is the primary system of record for delivery, a separate ALM platform can introduce operational friction. Jira-based test management add-ons or Azure DevOps may align better with day-to-day workflows. 3) Organizations that require full web client feature parity immediately Some reviewers note that the web client transition remains a work in progress and that certain features may be limited. Organizations with strict requirements to avoid client components should validate current web client parity in a hands-on proof of concept. 4) Price-sensitive organizations or those with small user counts User feedback often highlights licensing costs; smaller organizations can frequently achieve adequate coverage with lower-cost alternatives. 5) Organizations with complex integration requirements (Jira Cloud, multi-tenant, strict auth) If integration requirements include modern authentication patterns, event-driven integrations, or tight alignment with Jira Cloud, plan for dedicated integration engineering and possible middleware.

Deal disqualifiers (poor fit)

Small teams seeking a lightweight, low-administration tool
Teams fully standardized on Jira Cloud and unwilling to maintain a separate heavyweight ALM
Organizations that require fully browser-native experiences with minimal client components

Web client parity and transition limitations

Some reviewers report that the web version is progressing but still lacks full parity with legacy client functionality.

Browser/client and component management

Community discussions document practical issues with ALM Client Launcher workflows (browser launching, missing components, authentication failures). SSO setups may depend on default browser behavior and unsupported browsers can cause problems.

Reporting flexibility

Users frequently report that built-in reporting has limited flexibility and that custom reports or external BI tools are often used to supplement reporting needs.

Integration variability

Integration with Jira Cloud and other modern toolchains can require careful selection of plugins or middleware depending on organization requirements.

02Why they buy

Traceability and governance: the product provides established mechanisms to link requirements, test cases, and defects, supporting audit and validation processes.
Field and workflow customization: configurable fields and workflows accommodate enterprise process requirements.
Long operational history: the product lineage provides continuity for organizations migrating from older QC/ALM versions.

Competitive advantages of alternatives:

Modern user experiences and simpler onboarding are common differentiators for newer test management SaaS tools.
Jira-native add-ons reduce context switching for teams that already use Jira extensively.

- Traceability and governance: the product provides established mechanisms to link requirements, test cases, and defects, supporting audit and validation processes. - Field and workflow customization: configurable fields and workflows accommodate enterprise process requirements. - Long operational history: the product lineage provides continuity for organizations migrating from older QC/ALM versions. Competitive advantages of alternatives: - Modern user experiences and simpler onboarding are common differentiators for newer test management SaaS tools. - Jira-native add-ons reduce context switching for teams that already use Jira extensively.

03Field reports

Review platform signals (ratings, themes)

Gartner Peer Insights: vendor product page shows summary ratings and review counts; review text includes both favorable and critical observations.
G2: review volume and themes include positive feedback on end-to-end lifecycle tracking and recurring comments about UI and learning curve.
PeerSpot: review volume and average ratings show recurring notes about licensing cost, legacy UI, reporting limitations, and integration gaps.
Capterra: a listing exists and should be reviewed during procurement for additional user feedback.

- Gartner Peer Insights: vendor product page shows summary ratings and review counts; review text includes both favorable and critical observations. - G2: review volume and themes include positive feedback on end-to-end lifecycle tracking and recurring comments about UI and learning curve. - PeerSpot: review volume and average ratings show recurring notes about licensing cost, legacy UI, reporting limitations, and integration gaps. - Capterra: a listing exists and should be reviewed during procurement for additional user feedback.

Direct quotes (balanced)

Positive / favorable examples

Gartner Peer Insights (very positive review):
- “ALM has excellent customisations of the fields according to the projects. It also integrates well with UFT as well as Performance center (Loadrunner)”
G2 (positive reviews):
- “from requirements to test closure - ALM Does everything.”
- “linking requirements, test cases, and defects made it easy…”
G2 (recent favorable review):
- Likes: “managing the entire software development life cycle … at a single place… defect logging and tracking…”

Negative / critical examples

Gartner Peer Insights (critical review):
- “has accumulated a huge technical debt… web version is going in the right direction, but functionalities are still limited.”
PeerSpot (excerpts):
- “The initial setup was not straightforward.”
- “Reporting features are lacking in flexibility… manual workarounds.”
- “License costs are high…”

Positive / favorable examples - Gartner Peer Insights (very positive review): - “ALM has excellent customisations of the fields according to the projects. It also integrates well with UFT as well as Performance center (Loadrunner)” - G2 (positive reviews): - “from requirements to test closure - ALM Does everything.” - “linking requirements, test cases, and defects made it easy…” - G2 (recent favorable review): - Likes: “managing the entire software development life cycle … at a single place… defect logging and tracking…” Negative / critical examples - Gartner Peer Insights (critical review): - “has accumulated a huge technical debt… web version is going in the right direction, but functionalities are still limited.” - PeerSpot (excerpts): - “The initial setup was not straightforward.” - “Reporting features are lacking in flexibility… manual workarounds.” - “License costs are high…”

Why customers select this product (recurring reasons)

Common selection drivers referenced in reviews and vendor messaging include:

Traceability among requirements, tests, and defects
Workflow customization for enterprise governance
Centralization across large programs with many teams/projects
Integrations with OpenText testing tools (UFT, LoadRunner/Performance Center)

Why some customers leave or consider alternatives

Common churn drivers documented in reviews and community commentary include:

Licensing costs and perceived pricing complexity
Pressure to move to cloud-native, developer-centric tooling
User interface and perceived legacy architecture concerns
Integration friction with Jira Cloud/Azure DevOps and modern CI/CD pipelines

Vendor case study example: “The Department” (OpenText customer story)

OpenText publishes a customer story describing an organization using OpenText AQM to coordinate stakeholders and manage quality across the lifecycle.

Critical evaluation:

The publicly visible excerpt is qualitative; quantified outcomes (for example, defect reduction percentage, cycle time reduction, or audit cost savings) are not clearly presented in the snippet.
As with many vendor case studies, there is potential for selection bias. Procurement teams should request references and implementation specifics (team size, number of projects, integrations, and before/after baselines).

OpenText publishes a customer story describing an organization using OpenText AQM to coordinate stakeholders and manage quality across the lifecycle. Critical evaluation: - The publicly visible excerpt is qualitative; quantified outcomes (for example, defect reduction percentage, cycle time reduction, or audit cost savings) are not clearly presented in the snippet. - As with many vendor case studies, there is potential for selection bias. Procurement teams should request references and implementation specifics (team size, number of projects, integrations, and before/after baselines).

Vendor-reported metrics and proof points

Vendor pages include numeric claims of visibility or efficiency improvements.

Critical evaluation:

Such claims are marketing statements that may not include public methodology or sample details. Treat them as directional and request substantiation (baseline, sample size, measurement period) during procurement.

04Best fit

Company sizes

Large enterprises or multi-business-unit organizations
Mid-market organizations that operate in regulated industries and require formal validation and traceability

Industries / verticals

Representation observed in IT services, software, healthcare, banking, and telecommunications

Roles and personas

QA Directors / Test Managers
Release managers / PMO in regulated programs
Compliance / validation leads (life sciences, medical devices)
DevOps/toolchain owners responsible for cross-team governance

Best-fit pain points

Need for end-to-end traceability for audits
Centralized repository requirements for tests/defects across multiple products
Requirement for configurable workflows and approval processes
Existing investment in QC/ALM and a desire for continuity or a supported migration path

05The pitch

What the product does (core value proposition)

OpenText AQM is the successor to HP Quality Center / HP ALM and Micro Focus ALM/Quality Center (QC), now maintained by OpenText following its acquisition of Micro Focus. This lineage is relevant: some buyers select the product for its long-established workflow customization and traceability features; critics often cite technical debt, older UI paradigms, and administration complexity.

OpenText Application Quality Management (AQM) is an enterprise application lifecycle management (ALM) and test management platform used to manage requirements, test planning/execution, defect tracking, traceability, and audit-ready reporting across the software delivery lifecycle. OpenText describes it as a centralized interface for software quality management with governance and compliance capabilities aimed at regulated or complex environments. OpenText AQM is the successor to HP Quality Center / HP ALM and Micro Focus ALM/Quality Center (QC), now maintained by OpenText following its acquisition of Micro Focus. This lineage is relevant: some buyers select the product for its long-established workflow customization and traceability features; critics often cite technical debt, older UI paradigms, and administration complexity.

Target market and positioning

Primary target: large enterprises and regulated organizations needing traceability, auditability, and centralized governance across multiple projects/teams.

Positioning themes (vendor):

Auditable lifecycle processes and end-to-end traceability
Centralized platform for requirements, tests, and defects
Integrations with broader DevOps toolchains
Identity and access controls (SSO, RBAC, encryption) as part of governance messaging

OpenText offers multiple editions (e.g., Express / Enterprise / ALM) and provides Core (SaaS/managed) variants (see "OpenText Core Application Quality Management" service description).

Primary target: large enterprises and regulated organizations needing traceability, auditability, and centralized governance across multiple projects/teams. Positioning themes (vendor): - Auditable lifecycle processes and end-to-end traceability - Centralized platform for requirements, tests, and defects - Integrations with broader DevOps toolchains - Identity and access controls (SSO, RBAC, encryption) as part of governance messaging OpenText offers multiple editions (e.g., Express / Enterprise / ALM) and provides Core (SaaS/managed) variants (see "OpenText Core Application Quality Management" service description).

Get a comprehensive analysis of OpenText Application Quality Management including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →