Where the Two Platforms Differ
A comparison of how each platform structures coverage, handles changes and operates across application estates.
Eggplant
Virtuoso QA
Organising artefact
A model of application states and actions, built and maintained by your team
Requirements generated from your documents, each citing its source clause
Where coverage comes from
AI generates and prioritises paths through the model
Journey structures proposed from approved requirements, accepted by a person
Requirements handling
Keysight Generator reads a requirements file and produces Gherkin scenarios and manual test cases
Requirements are live artefacts; journeys record the requirement version they verify
When the specification changes
Your team updates the model and reusable snippets, then the AI re-explores
Affected requirements and journeys are flagged, with updates proposed as diffs
Human approval
Oversight of the model and the generated paths
A gate before anything becomes an asset, versioned against the requirement
How the UI is read
Image and text recognition, no DOM or object model dependency
DOM-based execution on a deterministic engine
Technology reach
Web, desktop, mobile, API, Citrix and VDI, mainframe, embedded, kiosk and proprietary GUIs
Browser applications, API and database validation within a single journey
Packaged engineering applications
A core strength, including SAP, Teamcenter, Windchill, NX, Creo and 3DEXPERIENCE
SAP, Salesforce, Dynamics 365, ServiceNow, Workday, Oracle and custom applications
Maintenance focus
The model, reusable snippets and visual references
The requirement chain, with repairs proposed and accepted per artefact
Standards across the suite
Modelling conventions your team defines
Agentic Directives applied at generation time, authored by you
Frequently Asked Questions
Common questions about model-based testing, requirements, approval and migration.
Eggplant tests Citrix, mainframes and embedded systems. Does Virtuoso QA?
Keysight Generator turns requirements into test cases. How is that different?
Is model-based generation not broader than requirement-based?
Is human approval optional in Virtuoso QA?
Can we keep our existing Eggplant assets?
































