Shared AI surface across the DevOps catalog
A single Aviator license plugs into Software Delivery Management, Functional Testing, Application Quality Management, and Performance Engineering. Customers do not buy one AI for each product.
OpenText • Application lifecycle management
OpenText DevOps Aviator
DevOps Aviator is the generative AI layer that rides on top of the OpenText DevOps catalog. Merito delivers the rollout that turns Aviator suggestions into evidence teams actually trust.
Merito sells OpenText DevOps Aviator and delivers AI rollout across the DevOps catalog and test generation, defect clustering, risk scoring, and review-ready release evidence that release managers sign.
- Best for
- QA Leaders rolling AI into test generation and defect triage, Release Managers adopting AI-generated release evidence, SDET Managers integrating Aviator suggestions into framework authoring
- Hosting
- SaaS
- Time to value
- First Aviator-generated artifacts in as little as a few days for narrow scope. First Aviator-generated artifacts in two to four weeks with a clean requirements and defect baseline. Meaningful adoption inside release ceremonies in three to six months.
- Security posture
- SOC 2 Type II, ISO 27001, GDPR
- Last reviewed
- 2026-04-26
What it is
OpenText DevOps Aviator in the enterprise stack
OpenText DevOps Aviator is a generative AI surface shared across the DevOps catalog. It reads from Software Delivery Management, Application Quality Management, Functional Testing, and Performance Engineering products and produces outputs that a release manager can act on and test cases generated from requirements, defects clustered by root cause, risk scores on release candidates, and narrative evidence suitable for governance meetings.
Aviator is not a standalone product in the sense that it runs tests or manages releases on its own. It runs inside the catalog. The license is priced and sold alongside the DevOps product it augments. Customers who own Software Delivery Management add Aviator to get AI-generated release narratives; customers who own Application Quality Management add Aviator to get test-case generation grounded in their own requirements.
Merito treats Aviator as a rollout problem, not a toggle. Getting useful AI output requires clean requirements, clean defect history, and an honest baseline of manual effort so improvements are measurable. Merito's engagement starts with the data layer and what history are you feeding Aviator, what outputs do you want from it, and which release ceremonies will adopt those outputs first.
Ideal use cases
- AI-generated test cases from requirements and user stories
- Defect clustering and root-cause grouping across release cycles
- Risk scoring for release candidates based on change scope and test coverage
- Review-ready narrative evidence for release governance meetings
- Feedback loops that turn defect closure patterns into test suggestions
What it is best at
Where OpenText DevOps Aviator earns its seat
Grounded in customer data, not generic model output
Aviator reads from the customer's own requirements, test history, defect backlog, and release outcomes. The suggestions are specific to the program's history, not generic LLM output.
Review-ready output for governance meetings
The release-narrative and risk-score outputs are designed to land in governance ceremonies. Release managers can accept, edit, or reject them inline; AI does not publish evidence on its own.
Core capabilities
OpenText DevOps Aviator capabilities, grouped by outcome
Test generation
AI-drafted test cases grounded in the customer's own requirements, stories, and existing test assets.
Requirement-to-test-case drafting
Aviator reads requirements in Application Quality Management or Software Delivery Management and drafts test cases ready for human review.
Story-to-acceptance drafting
Aviator takes agile stories and generates candidate acceptance tests aligned with the team's past patterns.
Gap analysis against existing tests
Aviator compares requirement scope against existing test coverage and proposes the missing tests.
Defect intelligence
Cluster, prioritize, and explain defects across release cycles using the program's own history.
Defect clustering
Aviator groups defects by likely root cause so triage teams see five clusters instead of five hundred tickets.
Defect prioritization
Severity and customer-impact scoring informed by the program's historical closure patterns.
Narrative summaries
Natural-language descriptions of defect clusters written for engineering leads and release managers.
Release intelligence
AI-generated release readiness evidence that governance bodies can review and sign.
Release risk scoring
A score for each release candidate informed by change scope, test coverage, defect trend, and past-release outcomes.
Release narrative generation
A written summary of what is in the release, what was tested, and what residual risk remains. Tuned for governance meetings.
Trend analysis
Cycle-over-cycle analysis of delivery health trends, surfaced as both dashboards and narrative copy.
Where it fits in the stack
How OpenText DevOps Aviator connects to the rest of your landscape
OpenText DevOps catalog (native)
Native- OpenText Software Delivery ManagementRelease narratives, risk scoring, and trend analysis generated from SDM data.
- OpenText Application Quality ManagementTest generation, gap analysis, and defect clustering inside AQM.
- OpenText Functional TestingAI-suggested automation steps and defect categorization from Functional Testing runs.
- OpenText Performance EngineeringAI-assisted scenario drafting and result interpretation inside LoadRunner editions.
DevOps toolchain (certified)
Certified- Jira, Azure BoardsRequirement and defect ingestion from popular work trackers.
- Azure DevOps, Jenkins, GitHub Actions, GitLab CIPipeline event ingestion so Aviator correlates build outcomes with release risk.
Custom (integrations Merito delivers)
Custom- Custom requirement and defect sourcesMerito adapters for proprietary requirement stores and legacy defect trackers that Aviator reads.
- SAML SSO and enterprise identityIdentity mapped from corporate IdP for governance-audit traceability.
Deployment and implementation
How it rolls out
- Hosting
- SaaS (North America, EMEA, APJ)
- Implementation complexity
- Moderate
- Typical time to value
- First Aviator-generated artifacts in as little as a few days for narrow scope. First Aviator-generated artifacts in two to four weeks with a clean requirements and defect baseline. Meaningful adoption inside release ceremonies in three to six months.
- Prerequisites
- A DevOps catalog product Aviator rides on (Software Delivery Management, Application Quality Management, Functional Testing, or Performance Engineering)
- Requirements, stories, or defect history clean enough to ground AI output
- Named governance meeting or ceremony that will adopt Aviator evidence first
- Aviator license appropriate to usage tier
- What Merito usually handles
- Merito handles Aviator enablement, data-layer preparation, first-ceremony adoption, and measurement of improvement. Merito does not publish AI-generated content without human review; every Aviator artifact is authored by AI and signed by a human.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- OpenText DevOps Aviator is subscription-licensed and priced on top of the underlying DevOps product (Software Delivery Management, Application Quality Management, Functional Testing, or Performance Engineering). Usage tiers vary by user count and AI call volume. Merito sells Aviator alongside the base product.
- Editions and modules
Aviator for Software Delivery Management
Release narratives, risk scoring, trend analysis inside SDM.
Best for: Programs using SDM for delivery governance.
Aviator for Application Quality Management
Test generation, gap analysis, defect clustering inside AQM.
Best for: Regulated QA programs needing AI-assisted authoring.
Aviator for Functional Testing
Test step suggestions, defect categorization inside Functional Testing.
Best for: Automation teams consolidating on OpenText Functional Testing.
Aviator for Performance Engineering
Scenario drafting and result interpretation inside LoadRunner editions.
Best for: Performance CoEs wanting faster scenario authoring.
- Common expansion areas
- Expanding Aviator across additional DevOps catalog products
- Higher usage tiers as AI adoption spreads across ceremonies
- Custom adapter work for proprietary data sources
- Training and enablement for governance bodies adopting AI evidence
Merito services
How Merito helps you win with OpenText DevOps Aviator
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
Aviator Rollout
Data-layer preparation, first-ceremony adoption, and measurement of AI-assisted improvement.
Explore service02DevOps Consulting
Aviator output wired into release ceremonies and CI/CD governance meetings.
Explore service03MAPS Assessment
Readiness assessment for customers considering Aviator across the DevOps catalog.
Explore service04Premium Support
Named engineer, priority SLAs, and release-time coverage for Aviator in production.
Explore service05Managed Services
Long-term run support for Aviator in high-volume programs.
Explore service06Training and Enablement
Author and reviewer training for teams consuming Aviator artifacts.
Explore service07Staff Augmentation
Merito-placed Aviator engineers embedded with your release and QA teams.
Explore serviceDevOps Aviator licensing
Buy Aviator from the partner that also walks it into your release ceremony.
Merito sells OpenText DevOps Aviator and delivers the rollout that turns AI drafts into evidence your governance bodies actually sign.
Merito point of view
Aviator success is an adoption problem, not a license problem.
Merito has seen customers buy Aviator, generate thousands of AI artifacts in the first month, and have zero of them land in a real release ceremony. That is an adoption failure, not a product failure. Aviator generates fine; the question is whether a governance body will accept AI-drafted evidence, and that question is not answered by the license.
Merito recommends picking one ceremony (release readiness review, defect triage, or test authoring) and adopting Aviator there first. Measure the before and after. If the AI draft saves the team time and the quality holds, expand. If it does not, the tuning work is the bottleneck, not the spend.
Aviator is priced per underlying DevOps product. Merito's advice and start with Aviator for the product that has the cleanest data. Software Delivery Management often leads because release data is easier to clean than test data. Application Quality Management leads in regulated environments because requirement quality is already a habit.
What buyers usually underestimate
- Buying Aviator before the DevOps product it rides on is operationally healthy.
- Expecting AI output to be adopted without a governance review cycle.
- Starting Aviator with dirty requirement or defect data and blaming the model.
- Skipping the before-and-after baseline so improvement is not measurable.
- Publishing AI-generated release narratives without a human sign-off step.
Related from Merito
Continue exploring OpenText DevOps Aviator on Merito
Related solutions
Related services
Related products
- OpenText Software Delivery ManagementRelease orchestration and governance that Aviator augments.
- OpenText Application Quality ManagementRegulated QA that Aviator grounds test generation in.
- OpenText Functional TestingFunctional automation Aviator reads from and suggests into.
- OpenText Core Performance EngineeringPerformance runs Aviator drafts scenarios for.
- OpenText (vendor portfolio)OpenText hub and the full DevOps and Content catalogs.
Frequently Asked Questions
OpenText DevOps Aviator FAQs
Consultation request
Talk to Merito about OpenText DevOps Aviator
Share which DevOps catalog product you own and which ceremony you want Aviator to land in first. A Merito Aviator specialist follows up within one business day.
One ceremony first
Measured adoption, not AI theater
Merito picks one ceremony, baselines manual effort, and expands Aviator only when the numbers move.
Human-in-the-loop by design
AI drafts, humans sign
No Aviator artifact ships without human review. Merito enforces that in every rollout.
Next step
Pick one ceremony. Prove the lift. Then expand.
A Merito Aviator engagement picks one ceremony (release readiness, defect triage, or test authoring), measures the baseline, and adopts Aviator there first.