The QEAgency.
Built on 25 years of QE experience
Specialized agents that share context across requirements, code, test, data, and operate as a closed loop.
Built For QE Teams — An Agency of Autonomous Agents.
01How It Works
Continuous verification. End-to-end.
Three steps from a staging URL to a self-healing test suite running in your CI — change reasoning, generation, healing, on a continuous loop.
Understand the change
myNova reads requirements, code diffs, and application history. It determines what must be tested on every change — and dispatches generation tasks to the rest of the system.
Generate verification
myGenie authors idiomatic Playwright TypeScript with role and label-based locators, then commits it. myNexa aligns test data and database state with the application — in parallel.
Run, heal, repeat
Tests run on every commit. When the UI changes, myAstra recomputes selectors from the page state graph in real time. The output of each agent feeds the next — closed loop, continuous.
02Platform Governance
Enterprise-grade access control.From org to agent — every layer governed.
MyDiya.AI is built for multi-organization enterprises. Onboard teams, structure projects, assign roles, and control which agents each user can access — all through a unified RBAC framework.
Organization Onboarding
Each enterprise or business unit exists as an isolated tenant — with dedicated workspaces, separate data schemas, and independent billing. Onboard organizations in minutes with zero cross-tenant data exposure.
- Schema-per-tenant isolation
- Independent workspace config
- Custom org branding
- SSO per organization
Project Management
Create and manage multiple QE projects within an organization. Each project maps to an application, a test scope, or a delivery team — with independent agent configurations and CI/CD pipelines.
- Project-scoped agent configs
- Per-project test suites
- CI pipeline bindings
- Cross-project reporting
User Roles & Auth
Fine-grained role-based access control ties every user to a permission profile. Roles are enforced at API, UI, and agent-execution layers — ensuring the right people have the right access, always.
- JWT + SSO authentication
- Role-scoped API access
- Audit log per user
- Invite & provisioning flows
Agent Assignment
Agents are assigned to users based on their role and project membership. A QE Lead has full access to all four agents; a Viewer can only read reports. Capability tokens enforce boundaries at execution time.
- Role-gated agent access
- Capability-scoped tokens
- Per-agent audit trail
- Lead-to-agent delegation
Role Hierarchy · Agent Access Matrix
| Role | myNova | myGenie | myNexa | myAstra | Projects | Reports | Settings |
|---|---|---|---|---|---|---|---|
| Org Admin | |||||||
| QE Lead | — | ||||||
| QE Engineer | — | — | — | ||||
| Viewer | — | — | — | — | — | — |
Onboarding Flow · Organization to Agent in 4 Steps
Create Organization
Register your org, configure SSO or email auth, and set workspace-level policies.
Create Projects
Map projects to your applications. Each project gets its own agent configuration and CI pipeline.
Invite Users & Assign Roles
Invite team members and assign roles — Admin, QE Lead, Engineer, or Viewer — per project.
Agents Activate by Role
Agents are automatically enabled per role. Capability tokens are issued at login — no manual wiring.
03Agent Library
Four agents. One closed loop.
Each agent has a defined cognitive scope, its own model, its own tools. They share state continuously — closed loop, not pipeline. The output of one becomes the input to the next.
Input → Output Flow
Each agent consumes distinct enterprise inputs and emits structured intelligence the next agent can act on.
Input
- •Website
- •User Story
- •Requirements
Output
- 1Optimized Steps
- 2Smart Locators
- 3Test Data
- 4API Discovery
- 5UI Bugs
- 6Screenshots
- 7Accessibility
- 8Performance Reports
Input
- •Optimized Steps
- •Locators
- •APIs
Output
- 1Automation Code
- 2Reusable Components
- 3AIME Reusable Graph
- 4Impact Analysis
- 5Branch Creation
- 6PR Raise
Input
- •Failed Execution
- •Logs
- •Screenshots
Output
- 1Refactored Code
- 2Root Cause Analysis
- 3Self-Healed Locators
- 4Fix Recommendations
Input
- •DB Schemas
- •Migration Scripts
- •API Payloads
Output
- 1Schema Changes
- 2Data Drift
- 3DB Impact Analysis
- 4Migration Validation
- 5Test Data Mapping
myNova
APPLICATION INTELLIGENCEIntent-Driven Application Intelligence Agent
Enterprise Purpose
myNova takes testing intent from Jira, Azure DevOps, test management tools, user stories, test cases, release notes, or direct user prompts, then explores the application intelligently.
Business Outcome
myNova converts scattered enterprise inputs into structured application intelligence, helping teams understand what to test, where risk exists, what changed, and what automation opportunities are available.
Integration Area & Enterprise Value
| Area | Enterprise Value |
|---|---|
| Jira / Azure DevOps | Understand user stories, defects, acceptance criteria, sprint scope |
| Test Management Tools | Read existing test cases and execution history |
| Web / Mobile Applications | Crawl and discover journeys, forms, validations, APIs, UI behavior |
| API Gateways / Postman Collections | Understand backend contracts and service behavior |
| CI/CD Pipelines | Trigger intelligence after deployment or release candidate build |
| Cloud Environments | Connect to QA, SIT, UAT, staging, and pre-prod environments |
| AIME Graph | Store application journeys, risks, validations, APIs, locators, and coverage intelligence |
04Use Cases
Four workflows the closed loop handles continuously.
What MyDiya does, exactly. No vague promises — these are the workflows the platform handles today.
Smoke suite from a URL
Point Browser Navigator at staging. It crawls the app, fingerprints page states, identifies critical user flows, and the Test Authoring agent emits a Playwright suite you can review and merge in minutes.
Record once, run forever
Hand-record a complex flow (multi-step approvals, frame-switching, downloads). MyDiya converts it to Playwright code with stable role/label-based selectors, auto-cleaning misclicks and retries.
Surviving UI churn
When a data-testid renames or a CSS class drifts, myAstra recomputes the locator from the page state graph — in real time, with no human in the loop. Maintenance debt stops compounding.
05Security
Trusted with your test estate.
Schema-per-tenant isolation, capability-scoped tokens, and audit trails — so QA leads can hand the platform to engineers without losing sleep.
Per-Agent Capability Tokens
Every agent carries a signed, attenuable token. Lock down what it can do — by workspace, project, tool, or time. Engineers can’t escalate scope.
Test-Run Safeguards
Hardware-Bound Identity
CLI keys stay in TPM / Keychain — never leave the engineer’s laptop.
Workspace Isolation
Schema-per-tenant DB isolation. Each QA team’s tests, secrets, and runs are walled off — with a full audit trail across them.
Trust Chain
Cryptographic Chain
HMAC-chained caveats
sig₀ = HMAC(rootKey, identifier)
sig₁ = HMAC(sig₀, caveat₁)
sig₂ = HMAC(sig₁, caveat₂)
... anyone can ADD a caveat, nobody can REMOVE one06Command Line
Tests from the terminal.
For QE engineers who live in the shell. Generate, run, and heal Playwright suites from the command line — and from your CI runners.
Connected · Offline
Switches automatically — full platform online, degraded on flaky CI runners, fully offline behind a firewall.
Sandboxed by Default
Every test run is sandboxed. Repo-root isolation, file-write allowlist, no shell escape.
CI-Native Output
JUnit XML, TestRail, JSON report. Plug into Jenkins / GitHub Actions / GitLab CI in one line.
07Help & Support
Need a hand? We're here.
Reach out and a real human from the MyDiya team will get back to you — usually within one business day.
Email support
Prefer email? Drop a line and we'll route it to the right person.
Support
support@ascendqe.com