This interactive demo mirrors the full Virtuoso QA desktop interface, so it needs a wider screen to be readable.
Open it on a laptop or desktop for the full walkthrough, or continue here and pinch to zoom.
Walk through a guided demo: load your Knowledge Base and see how an AI Analyst, and an AI Architect turn legislation into requirements and human-approved test journeys.
The AI Autopilot then writes a deterministic Virtuoso NLP test, which runs with self-healing selectors - giving you robust, governed QA that's always mapped back to a valid requirement.
From the project dashboard you can create shiny new goals - a testing scope within a project.
The Knowledge Base is a centralised repository of sources that our agents can use to build your requirements from.
| Sources | Tags | Last change | |
|---|---|---|---|
| Microsoft Dynamics 365 Sales Professional: Create Account and Opportunity BRDNEW Project | 0 | 08/09/2026, 09:14 PM | |
| Sarbanes-Oxley Act (SOX) - IT General ControlsNEW Project | 0 | 08/09/2026, 09:14 PM | |
| UK GDPR / Data Protection Act 2018NEW Project | 0 | 08/09/2026, 09:14 PM | |
| ISTQB Certified Tester Foundation Level SyllabusNEW Project | 0 | 08/09/2026, 09:14 PM | |
| IT Governance Framework (COBIT-aligned)NEW Project | 0 | 08/09/2026, 09:14 PM |
| Requirements | Risk | Coverage |
|---|---|---|
| Account and Opportunity Creation Negative Scenarios | HIGH | 100% |
| Successful Account Creation | CRITICAL | - |
| Successful Opportunity Creation and Association | CRITICAL | 100% |
Sources selected:
The existing requirements provide good coverage for the primary success paths. However, I identified three gaps not explicitly covered by the BRD:
I've generated three new requirements to close these gaps, applying the organisation's ISTQB-Aligned Test Analysis directive throughout.
| Requirements | Risk | Coverage |
|---|---|---|
| Non-Functional Requirements for Account and Opportunity Management | MEDIUM | - |
| Authorization Controls for Account and Opportunity Creation | CRITICAL | - |
| Opportunity Creation Validation Rules | MEDIUM | - |
| Account and Opportunity Creation Negative Scenarios | HIGH | 100% |
| Successful Account Creation | CRITICAL | - |
| Successful Opportunity Creation and Association | CRITICAL | 100% |
The purpose of this requirement is to ensure that the system meets essential non-functional standards for performance and auditing during the creation of Accounts and Opportunities. It specifies that field validation must occur within 1 second and save operations within 3 seconds, while also confirming the generation of audit trails for each successful record creation.
This requirement validates that the system meets the specified non-functional requirements for performance and auditing during the Account and Opportunity creation processes.
Requirement: Non-Functional Requirements for Account and Opportunity Management
I have designed five test journeys to validate the non-functional requirements for performance and auditing, as specified in this requirement.
These journeys cover:
I've created corresponding data tables to drive these tests and a new environment for the base URL. Please review the proposed journeys.
Checkpoint 1: Navigate to New Account Form
Assuming the user is already logged in, go to the base URL, open the Accounts section, and click "New" to start a new Account record.
Checkpoint 2: Fill Form and Measure Save Time
Enter a value into the Account Name field, then start timing. Click Save, wait for the page to reload, and stop timing once it's finished. Assert that the whole save operation completed in under 3 seconds.
This journey measures the time taken to save a new Account record and asserts that it is within the 3-second threshold.
There are no plans associated with this journey.
"Accounts""Accounts""New""Accounts""Accounts""New" 🩹 healed"New" 🩹 healed"Account Name""Save"