Skip to content

Releases: QAIA-Project/QAIA

Release list

v0.1.0-prealpha — first tagged snapshot

v0.1.0-prealpha — first tagged snapshot Pre-release
Pre-release

Choose a tag to compare

View all tags
@Opaland Opaland released this 07 Aug 23:12
v0.1.0-prealpha
2083a67

Pre-alpha. No human pilot has ever run QAIA end to end. This tag exists so the state of the project on 8 August 2026 has a name, not because it is ready for your production QA process.

What QAIA is

Four Claude Code plugins — 30 Markdown skills — that take a user story to a traceable Gherkin test book and then to runnable native Playwright tests. No API key, no backend, and nothing installed into your repository that executes on its own.

/plugin marketplace add https://github.com/QAIA-Project/QAIA
/plugin install qaia-core@qaia

qaia-core alone covers user story to test book. The rest are optional.

Plugin Version Skills
qaia-core 0.2.30 15
qaia-playwright 0.1.20 11
qaia-score 0.2.0 3
qaia-testdata 0.1.1 1

What is actually proven

  • A suite generated by the automate skill runs on a GitHub Actions runner with no Claude session, no skill loaded, nothing from plugins/ read — 8 tests, 8 green (run 30702503888, raw log kept in eval/ci-proof-2026-08-01/).
  • Two independent domains taken end to end: finance/HR (examples/expense-demo/, 38 traced scenarios from one story, 43 green Playwright tests) and a healthcare-shaped domain (examples/medibook/, 32 green tests).
  • All 32 manifests in the repository pass the validator, and CI enforces it.
  • Every skill carries a verdict from a real run, unfavourable ones included.

What is not proven, stated plainly

  • No human pilot. Everything measured about QAIA was measured by harnesses, CI and personas — never by a QA engineer doing their actual job.
  • An external 13-persona audit scored QAIA 2.4/5; an architecture review scored it 5.0/10. Both are in docs/STATUS.md with what was fixed and what was not.
  • The quality of what QAIA produces for a real user is unmeasured. That is the biggest open question in the project and it is not close.
  • No regulatory framework is mapped. The healthcare example demonstrates traceability on a healthcare-shaped domain — not IEC 62304, not 21 CFR Part 11, not ISO 13485.

Where to look without installing anything

The most useful thing you can do

Try it and tell us where it disappoints. Right now an issue describing exactly how it failed you is worth more to this project than a star.

Loading