Resources

Guides and resources

Practical, experience-based guides on test creation, AI-assisted automation, self-healing, and suite health, written for QA practitioners.

Test creationAI automationSelf-healingSuite health
Project · Overview
Health
A
up 6
Tests
248
up 12
Pass rate
94%
up 3%
Coverage
72%
up 5%
Coverage trendup 32% vs last 14 days
Automation
9 / 9 automated100%
Last run
Sign in
Add to carthealed

The library

12 guides, no fluff

Each one is a working playbook you can apply this sprint, whether you test by hand or with AxonQA.

4 min read
Import & Export

Import your test cases from Excel or CSV

Bring your spreadsheet test cases into AxonQA in one upload. Columns map automatically, each row becomes a case with its steps and expected results, and you can export, edit, and re-import at any time.

Read guide
4 min read
Test Creation

Turn a user story into test cases

Import a story or write one here, and Axon expands its acceptance criteria into happy-path, negative, and edge cases, each traceable to the criterion it verifies.

Read guide
4 min read
Automation

Record or generate automation you own

Capture a real flow in the browser or draft automation from your case steps. Either way you get a maintainable page-object framework you can download, read, and extend.

Read guide
5 min read
AI Assistant

Run your whole regression from a sentence

Ask Axon in plain English to run your tests by description or tag, on the browsers you name. It launches in the background and reports back, so anyone on the team can run the suite.

Read guide
4 min read
Cross-Browser

Cross-browser testing without the setup

Run the same tests across Chrome, Firefox, and WebKit in the cloud, with a separate verdict for each browser and no machines to build or maintain.

Read guide
5 min read
API Testing

Test your APIs alongside your UI

Organize requests into collections, chain them into real flows, run them against any environment with datasets, and verify the contract your interface depends on.

Read guide
5 min read
Discovery

Ground the AI in your real app

Feed Project Brain your documents, screenshots, and imported stories, and let app discovery map your running product, so generation uses real selectors and journeys instead of guesses.

Read guide
5 min read
Self-Healing

Self-healing that tells a moved locator from a real bug

Four escalating tiers, deterministic first. When Axon reasons about a failure it reads the whole live page and tells a moved locator from a genuine bug, never faking a pass, and every fix is reviewable.

Read guide
4 min read
Requirements

Catch requirement drift before it ships

Axon watches your Jira or Azure work items, spots an acceptance-criteria change, shows every project member the diff, and generates suggested tests for the change in one click.

Read guide
5 min read
Insights

Track release readiness

Coverage, AI-powered dashboards, scheduled stakeholder reports, and alert rules to Slack, Microsoft Teams, or email turn scattered results into a clear answer to are we ready to ship.

Read guide
5 min read
Security

Test apps behind a login or private network

The local agent runs inside your network and connects outbound only, so a one-time pairing lets you crawl and test apps behind a login, including multi-role journeys, without opening a door in.

Read guide
4 min read
Integrations

Bring your own AI agent

AxonQA speaks the Model Context Protocol, so assistants like Claude Desktop and VS Code, and any MCP-compatible client, can generate cases, run suites, and read results end to end.

Read guide

Inside AxonQA

These practices, built into the product

The guides describe how we think about test quality. The product runs on the same ideas: tests grounded in your real requirements and flows, self-healing that escalates from instant deterministic fixes to careful AI review, and health metrics that make flakiness impossible to ignore.

  • Healing escalates in four tiers, cheapest and most certain first.
  • The AI is a last resort, and it tells a changed app apart from a broken one.
  • Every fix is recorded with the tier it came from, and is reviewable and reversible.
Self-healing · escalating tiers
0
Tier 0: Structural repair

Broken imports or malformed code that stop a test running.

1
Tier 1: Deterministic locator

Instantly tries known alternative ways to find the same element. No AI.

2
Tier 2: Timing and flakiness

Waits for elements, scrolls into view, adjusts timeouts.

3
Tier 3: AI reads the whole page

Decides: did the element move (heal it) or is the app actually broken (flag a real bug)?

Healing shows in amber, and never rewrites what your test expects.

Put these practices to work

Generate structured test cases from your stories, then validate them with real runs on your own app.

Get StartedBook a Demo