Vision and requirements

Vision

Help someone learning or comparing test tools see the same testing idea side by side across open-source frameworks — unit, TDD, BDD, HTTP integration, browser UX, performance, and security — with runnable samples and answers grounded in this repo.

The product is an educational Rosetta site, not a hosted test runner and not a replacement for official framework docs.

Who it is for

• Engineer learning a second stack: Open one scenario and switch frameworks without changing the idea
• Team standardizing or migrating tools: Compare idioms on the same SUT before picking a default
• Educator or interview coach: Point at a short, parallel example instead of inventing one
• Maintainer / agent: Keep scenario JSON, samples, and this document honest

In scope

1. Compare the same scenario in more than one framework — do not just catalog tools.
2. Cover the testing pyramid and beyond: unit, integration, UX, performance, and security.
3. Use open-source frameworks and a free-to-run hosting path only.
4. Stay at zero cost for the public site: GitHub repo, Actions, and Pages.
5. Answer “how do I do X in Y?” from this corpus, not from generic internet inventiveness.
6. Teach by doing: small samples visitors can clone, plus CI-cached run output on each scenario page.

Out of scope

• Paid SaaS test platforms (device clouds, commercial synthetics) as primary examples
• A replacement for official Vitest, Playwright, k6, or other vendor docs
• Running arbitrary visitor code in the browser or through a live execute API
• Multi-tenant accounts, billing, or enterprise SSO
• A complete catalog of every test tool in a language

Shipped requirements

19 functional, 7 non-functional, and 9 UX requirements are marked Shipped. IDs and status live in the GitHub document.

Constraints

• The site compares frameworks; it must not imply it is the official documentation for any of them.
• Answers on Ask AI must cite this repo (FAQ or scenario ids) or refuse.
• GitHub project Pages requires a `/TestingRosettaStone` base path in production.
• Cached Results logs are only as fresh as the last successful `capture:results` on `main`.