Docs & Resources
Learn what AxonQA does, how to use it end to end, and how we protect your data.
Start here
New to AxonQA? Begin with these.
Two ways to bring in requirements
Requirements do not only come from a tracker. Import epics and user stories from Jira or Azure DevOps, or create and write them directly inside AxonQA yourself. Either way, they become the grounding for AI test generation.
As a customer, I can sign in so that I can access my account.
Guides
How to use the system, step by step.
Requirement drift
Never test against stale requirements
When a ticket you imported changes, AxonQA detects it in near real time and, if the acceptance criteria changed, shows you exactly what is different. Review the difference and generate suggested tests for just the new or changed criteria, in one click. Your test suite never changes on its own.
A locked-out user sees a clear message and cannot sign in.
Reset links expire after 24 hours 1 hour.
Guests can check out without an account.
Self-healing
Four escalating tiers, cheapest and most certain first.
Most breaks are repaired before any AI is involved. The AI only steps in as a last resort, and when it does, it reads the entire live page and reasons about what actually changed.
- Tier 0: repairs structural problems that stop a test running at all, like broken imports or malformed code.
- Tier 1: a deterministic locator healer that instantly tries known-good alternative ways to find the same element, with no AI and no cost.
- Tier 2: rule-based fixes for timing and flakiness, such as waiting for an element, scrolling it into view, or adjusting timeouts.
- Tier 3: only here does the AI step in, reading the entire live page to decide between a locator that moved and an app that is genuinely broken.
The intelligence is that it tells the app changed apart from the app is broken. It safely heals a moved or renamed element, but flags a genuine bug rather than papering over it, and it never fakes a pass by rewriting what your test expects. Every fix it applies is reviewable and reversible.
Broken imports or malformed code that stop a test running.
Instantly tries known alternative ways to find the same element. No AI.
Waits for elements, scrolls into view, adjusts timeouts.
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.
Data protection & security
How your data is handled and kept private.
Trust & compliance documents
Request the documents your team needs for review.
Need something not listed here? Email privacy@axonqa.com and we will help.
Ready to try it yourself?
Create a project and generate your first test cases in minutes.