Aura QA · product
A test suite that maintains itself, inside your network.
Alignment before generation. Intent-anchored healing. Three deployment topologies down to fully air-gapped. Below is how each of those actually works.
Authoring
Discovery-first. You approve the plan before tests exist.
Healing
Intent-anchored, verified before commit.
Deployment
Managed, your VPC, or air-gapped on local models.
Runs on
Your existing Playwright or Selenium estate.
§1 Architecture
Model and eval layer
Four stages, each with its own gate. A candidate never reaches your suite without passing the one above it.
crawl
Headless traversal of the running app; builds a flow graph from reachable states and forms.
no model calls
rank
Flows scored on risk: money movement, PHI access, auth boundaries, irreversibility.
local model
align ⟶ you
Alignment Report issued. Human gate — covered and skipped flows both explicit.
blocking
generate
Tests emitted as readable Playwright in your repo — reviewable, diffable, yours.
local model
evaluate
Mutation-style checks: does each test actually fail when the behaviour it guards is broken?
deterministic
A generated test that still passes when you deliberately break the feature is worthless. The evaluate stage exists to catch exactly that, and it runs on every generation.
§2 Integration
Where it sits in CI
A container in your pipeline. It reads the repo, writes a branch, and opens a PR — the same review path as any other change.
git push
build + deploy preview
aura run + heal
PR: healed diffs
merge or escalate
# .github/workflows/qa.yml - uses: techfy/aura-qa@v1 with: endpoint: https://preview.internal models: ollama://qa-runner.internal egress: deny
Works alongside GitHub Actions, GitLab CI, Jenkins, and Azure DevOps. Issues route to Jira or Linear. Fit is validated in discovery before any build starts.
§3 Limits
What it does not do
Stated plainly, because you will find out in week two anyway.
Native mobile
Web only today. iOS and Android are not on the near roadmap.
Load and performance
Functional correctness only. Keep your existing performance tooling.
Pixel-level visual diffing
We assert behaviour, not appearance. Pair us with a visual tool if you need both.
Zero-touch operation
Ambiguous heals escalate by design. Someone on your side owns the queue.
Two design partner slots for 2026.
30 minutes with the technical team. Bring your worst-maintained suite.