Explore the application
Map reachable pages, controls, and journeys in a public app with cloud discovery, or use the local AxonQA Agent for a private environment.
Axon
Ask for the QA work. Watch it happen in your project.
Ask Axon to start AxonQA test generation, run checks, investigate failures or prepare a bug. AxonQA generates the cases; Axon coordinates work across your project and brings back the actions, results and evidence in one conversation, with your workspace permissions and approval controls.
200+ connected QA actions across test design, execution, investigation, integrations, and reporting.
14-day trialNo card requiredSample project included
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
Illustrative sample project. The sequence plays once; use the steps to explore or replay it.
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 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
Ask AxonQA to draft test cases from requirements, stories, and captured application evidence, then organise them under the project structure you choose.
Run and keep watching
Start browser runs by description or tag, default to Chrome in AxonQA Cloud, choose other browsers or Local when needed, chain runs by outcome, and rerun only what failed.
Build gated release test plans
In one instruction, create a named plan with separate smoke and full regression phases, run regression only when the smoke gate passes, attach the finished report to the right release, and get the result back in Axon.
Build API workflows
Import API definitions, create collections and chained flows, add assertions and schemas, then run public APIs in the cloud or private APIs through the local agent.
Investigate failures
Bring together the failed step, error, recent run history, healing events, and evidence captured by the run so the team can understand what went wrong.
Repair interface drift
Review and apply a validated locator replacement, then rerun the affected test. Axon can repair how a test finds something, never what the test expects.
Draft and file bugs
Prepare a ticket with a title, description, evidence, steps, expected result, and actual result, then file it in Jira or Azure DevOps after confirmation.
Work with requirements
Search and import Jira or Azure DevOps work items, read acceptance criteria, update supported fields, add comments, and apply valid transitions.
Move tests both ways
Preview and import cases from TestRail, Azure DevOps Test Plans, or Zephyr Scale. Create or update TestRail and Azure cases after confirmation, with durable links that prevent duplicate exports and surface remote-edit conflicts.
Schedule and report
Set recurring runs and reports, continue supported long jobs in the background, and return the result to the same conversation when they finish.
Conditional test plans in one instruction
Describe the plan. Let Axon run the gates.
Ask Axon to create a named test plan, run smoke first, start full regression only when its saved condition is met, and connect the completed report to the release you named. Axon keeps watching and brings the result back to the same conversation.
Axon · Release workflow
QA lead
Create and run a test plan called Test Plan Release 2.5 for Release 2.5. Run @smoke first. If it passes, run full regression. If smoke fails, stop. Attach the report and let me know the results.
Task·step 1 of 5
Create Test Plan Release 2.5Create plan
Run the @smoke automation phase
Check the no failures gate
Run the full automation regression
Attach to Release 2.5 and notify
With no browser or execution target named, Axon uses Chrome in AxonQA Cloud. The two automation phases stay distinct, and only the saved smoke gate can unlock full regression.
Evidence returned in the chatRelease 2.5 · Staging
Test Plan Release 2.5 is ready.
Axon created two separate automation phases and saved the condition between them.
Smoke
Automation · @smoke · 6 tests
Continue only when no smoke tests failed
Full regression
Automation · all runnable tests · 42 tests
Release 2.5StagingChrome · AxonQA Cloud
A complete cycle takes about 15 seconds. Choose a stage, pause, or replay.
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 · 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 · Raise a bugExample
QA lead
Raise a bug for the failed checkout test.
BugPayments, Azure DevOps
Checkout: “Place order” unresponsive after entering card details
Description: Checkout stalls after valid payment details are entered. The customer cannot complete the order; the failed run captures the unresponsive button.
- 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, description, 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 · 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 · API workflow
QA lead
Create a Checkout API collection from the OpenAPI URL I provided, build and run a four-step checkout flow, and add six assertions including that $.total equals 49.99.
Outcome·6 stages
Checkout API workflow is ready and passing.
34 endpoints · 4 chained requests · 6 assertions
create_api_collectionCheckoutimport_api_from_url34 endpointscreate_api_flowCheckout flowadd_api_flow_step4 requestsadd_api_assertion6 checksrun_api_flowall passedOpen the flowShow assertions
API testing from the conversation
Build and run the whole API flow.
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.
Move test cases both ways
Review the destination before test cases move.
Ask Axon to import a suite from TestRail, Azure DevOps, or Zephyr Scale. After review, it can create or update linked cases in TestRail and Azure Test Plans, or create a TestRail project for a new library.
- Keep the destination project, epic, story, plan, suite, or section explicit.
- See the exact case count and destination before an external write.
- Update linked cases without duplicates; preserve and report independent remote edits.
Axon · Import test casesExample
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
Aware of the page you are on
Stay on the page. Ask Axon what it means or what to do next.
Get help with the work in front of you. Axon uses the available page and project context to explain results, help investigate a failure or carry out a supported task. Start with a question about what you are looking at.
- Ask “Explain this page” for a clear walkthrough of the available information.
- Ask about the current results, failures or coverage, then follow the supporting evidence.
- Request a supported task for the current page, such as adding a request to this flow or preparing a bug from this failed run.
- Your permissions still apply. Axon asks for missing details and required confirmations before proceeding.
Axon Example prompts
Your page. Your next step.
See how the conversation changes with the work you have open.
Reports and analytics
Understand what you are seeing
“Explain these results. What should I look at first?”
Get help interpreting the available metrics and finding the evidence to investigate.
A failed test run
Turn a failure into a useful bug
“Prepare a bug for this failed test.”
Review a draft with a description, reproduction steps, expected and actual results, and available run evidence.
API flow builder
Keep building without leaving the flow
“Add the login request to this flow.”
Ask Axon to add a saved request to the flow you have open, with any missing details clarified along the way.
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
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 alter a frozen verdict or accept risk on someone's behalf. An authorised user can explicitly request a separate, permission-checked change to the project's readiness policy.
Built to act safely
See the work. Control consequential changes.
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 adds the project context, side drawer, durable follow up, and notifications. MCP gives your own agent access to the underlying QA tools.
Give Axon your first QA task.
Start with the sample project. Ask about its coverage, inspect a failed check, and follow the evidence behind the release assessment.
14-day trial · No card required · Sample project included