Get your first workflow running.
Start with the sample project, connect your requirements, then create and run your own tests. Search for a task or choose a guide below.
New to AxonQA?
Open the worked sample project in your trial to explore connected tests, runs and release evidence. Then use the guides below to set up your own workflow.
Preview the sample report before signing up →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
Healing that repairs drift without hiding a failure.
Most breaks are repaired before any AI is involved, so healing stays fast and cheap. Reasoning is a last resort, and it is there to make one judgement: did the app change, or is the app broken?
- Cheapest first: fast, certain checks run before anything expensive, so most breakages are resolved without AI cost or delay.
- AI as a last resort: reasoning is reserved for failures the quick checks could not settle, which keeps healing predictable and affordable.
- A strict boundary: locator drift can be repaired; an assertion mismatch stays red with evidence for review.
- Nothing silent: every fix is recorded, reviewable and reversible, and no heal ever rewrites what your test expects.
AxonQA can safely heal a moved or renamed element. If the expected behaviour does not match, the assertion stays red with evidence for review. It never fakes a pass by rewriting what your test expects, and every locator fix is reviewable and reversible.
Same run, two very different causes.
The app changed, the test did not need to. Fixed during the run, and reversible.
The expected total did not match. Left red with evidence for review.
Cheap, certain checks run before anything expensive, and no fix ever 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?
Explore the sample project, then bring in your own requirements and test a workflow.
14-day trial · No card required · Sample project included