Explore the application
Map reachable pages, controls, and journeys in a public app, or use the local AxonQA Agent to reach a private environment.
Axon AI
Ask for the QA work. Watch it happen in your project.
Axon is the assistant inside AxonQA. It works from the side of the screen while your project, tests, runs, and evidence remain in view. Ask for an outcome in plain English, then follow every action and result in the same conversation.
200+ connected QA actions across test design, execution, investigation, integrations, and reporting.
AAxonQA
DashboardProjectsAutomationReports
Meridian Storefront
Fair · 63shop.meridian.com · E-commerce · web
Project healthLast 14 days
63
Health
84%
Coverage
0
Failed
Quality trend
Run outcomes, last 14 days
PassedFailed
Release 4.2 needs attention
Coverage target and one critical smoke check are outstanding
Axon stays in the side drawer while the project and its evidence remain visible. The full sequence takes about 15 seconds.
01
Understand
Read the app, requirements, and project evidence.
02
Create
Draft and organise the tests the work needs.
03
Execute
Run browser and API checks, even in the background.
04
Follow through
Investigate, report, and prepare the next action.
What Axon AI can do
One assistant across the QA workflow.
Axon does more than answer questions. It can take the project from understanding the work to creating, executing, investigating, and reporting it.
Create grounded tests
Draft test cases from requirements, stories, and the application itself, then organise them under the project structure you choose.
Run and keep watching
Start browser runs by description or tag, choose browsers, chain runs by outcome, and rerun only what failed.
Build API workflows
Import API definitions, create collections and chained flows, add assertions and schemas, then run the workflow from the conversation.
Investigate failures
Bring the failed step, run history, recording, and available evidence together so the team can understand what actually went wrong.
Repair interface drift
Replace a broken locator during a run and recheck the step. Axon can repair how a test finds something, never what the test expects.
Draft and file bugs
Prepare a ticket with the evidence, steps, expected result, and actual result, then file it in Jira or Azure DevOps after confirmation.
Work with requirements
Import Jira and Azure DevOps stories, add comments, and move issues through the transitions available to the project.
Bring existing tests
Preview and import cases from TestRail, Azure DevOps, or Zephyr Scale, filed under the epic or story you name.
Schedule and report
Set recurring runs and reports, continue long jobs in the background, and return the result to the same conversation when they finish.
See Axon at work
A clear response for every kind of job.
Each example below uses the same response patterns as the product. The run, evidence, choices, and next step stay visible instead of disappearing behind a generic chat answer.
Run it and get the result back
Ask for a run. Leave if you need to.
Tell Axon which tests to run and on which browsers. It starts the work, keeps watching in the background, and returns the result to the same chat with the pass count, failures, and useful next actions.
- Run by description or tag on the browsers you choose.
- Chain a larger suite to the result of a smoke run.
- Rerun only failures, then receive a notification when the work finishes.
Axon AI · Run and report
QA lead
Run the smoke suite on Chrome and Firefox, then tell me how it went.
RunRunning
Running 25 tests across two browsers
Watching the run in the background
Axon AI · Raise a bug
QA lead
Raise a bug for the failed checkout test.
BugPayments, Azure DevOps
Checkout: “Place order” unresponsive after entering card details
- 1. Enter valid card details on the payment step.
- 2. Click “Place order”.
- 3. Observe the button does not respond.
Expected
Order is placed and a confirmation is shown.
Actual
Button does not respond; no confirmation appears.
Recording attached Iteration 24
Axon
Here is the bug I will raise in Azure DevOps. Happy for me to file it into Iteration 24?
Yes, raise itEdit
From failure to a useful bug
The evidence arrives before the ticket is filed.
Ask Axon to turn a failed test into a bug. It prepares the title, reproduction steps, expected result, actual result, run recording, and destination so the team can review what will be written.
- Use the failed step and recording instead of rewriting the incident from memory.
- Choose Jira or Azure DevOps and the correct sprint or iteration.
- Review and edit the draft before Axon files it.
Coverage you can act on
Ask what is missing, not just for a percentage.
Axon reads the project stories and tests, explains coverage against the target, lists the exact gaps, and can continue straight into drafting the missing cases.
- Grounded in the stories and tests already in the project.
- The specific untested requirements remain visible in the answer.
- Move from a coverage gap to a reviewed test draft in the same thread.
Axon AI · Coverage
QA lead
What is our coverage, and which stories still need tests?
Insight·Sample Storefront
Coverage is below target
72% coverage4 gaps80% target
Coverage · Stories
Target 80%72%8% below target18/25 stories
Stories with no tests
STORE-208Refund a paid order
STORE-214Save a card for later
STORE-219Split payment across cards
STORE-231Guest checkout
You are at 72%, just under the target. Four stories have no tests, led by refunds and saved cards.
Draft tests for theseShow all gaps
Axon AI · API workflow
QA lead
Import our OpenAPI spec, build a checkout flow, and assert that the totals are right.
Outcome·5 actions
Checkout API workflow is ready and passing.
34 endpoints · 4 chained requests · 6 assertions
import_api_spec34 endpointscreate_api_collectionCheckoutcreate_api_flow4 chained stepsadd_api_assertiontotals verifiedrun_api_flowall passedOpen the flowShow assertions
API testing from the conversation
Build and run the whole API flow.
API work is not a small add on. Axon can import an OpenAPI definition or WSDL, build collections and chained requests, configure environments and data, add assertions and schemas, then execute the flow.
- Create endpoints, folders, environments, variables, and datasets.
- Assert responses and contracts rather than checking them by eye.
- Use mock servers, webhook inboxes, certificates, and a local agent for private services.
Bring your existing test library
Preview the import before anything changes.
Ask Axon to find a suite in TestRail, Azure DevOps, or Zephyr Scale. It shows what it found, where the cases will go, and how many will be created before asking for confirmation.
- Keep the destination project, epic, or story explicit.
- See a useful preview before any test case is written.
- Change the destination or cancel without losing the conversation.
Axon AI · Import test cases
QA lead
Import the Payments suite from TestRail into this project, under the Checkout epic.
TestRailPayments, Checkout suite
47 test cases ready to import
Into Mobile QACheckout epic
- · Guest checkout with a saved card
- · Apply a discount code at checkout
- · Decline on an expired card
- +44 more
Axon
Found 47 cases. I will file them under the Checkout epic. Go ahead?
Import 47 casesChange the epic
Ask what is blocking release
The release system calculates it. Axon explains it.
Release readiness is computed from the current project evidence and the conditions your team configured. Axon retrieves that assessment, explains the verdict and blockers in plain language, and helps with the next steps.
Project evidence
Tests, runs, coverage, bugs, and accepted risks
The evidence already held by the project is the input.
Release system
Evaluates the configured release conditions
The same evidence and conditions produce the same auditable assessment.
Axon AI
Explains the verdict and helps resolve blockers
Axon does not invent, recalculate, or override the assessment.
The calculated verdict and the human decision remain separate.
Axon can explain the assessment and carry out work that addresses a blocker. It cannot change the release conditions, alter the calculated verdict, or accept risk on someone's behalf.
Built to act safely
Useful because it can act. Trustworthy because the work stays visible.
Axon keeps the request, actions, evidence, and outcome together so the team can see what happened and retain control over consequential changes.
It asks instead of guessing
When a request is ambiguous, Axon asks a question before it acts on an assumption.
Important writes stay visible
Destructive and selected high impact actions require approval. Supported filing and import flows show a preview first.
The work stays traceable
The conversation keeps the actions and outcomes together, while writes retain who, what, and when in the audit trail.
Or bring your own agent
Give your own AI access to the same QA action surface.
The same 200+ actions are available over the Model Context Protocol. Axon AI adds the project context, side drawer, durable follow up, and notifications. MCP gives your own agent access to the underlying QA tools.
Ready to see AxonQA on your own app?
Create a project and generate your first test cases in minutes.