// About
Why qa.codes exists.
Quality engineering knowledge is scattered. The good stuff is spread across old blog posts, buried Stack Overflow threads, framework docs, half-finished tutorials, and bookmarks you never find again. Some of it is outdated. A lot of it assumes you already know the thing you came to learn.
qa.codes started as a fix for that — a single, current, trustworthy home for the tools, references, and guides that testers actually use. The kind of resource I kept wishing existed while piecing it together myself, one bookmark at a time, across a QA career.
The name says it: QA + code. It's where quality engineering lives.
What it is
qa.codes is a reference hub for software testing. In one place you'll find:
- Tools
- 200+ testing tools across the ecosystem, organized so you can actually find the right one
- Cheat sheets
- Copy-paste-ready references for the frameworks and commands you use daily
- Roadmaps
- Guided paths from manual testing into automation and specialist tracks
- Glossary
- 190+ testing terms, clearly defined and cross-linked
- Resources
- Snippets, configs, patterns, and templates you can lift straight into your work
- AI
- How testing is changing as AI enters the workflow, for both testing AI features and testing with AI
- Utilities
- In-browser formatters, generators, and converters for everyday QA work
Everything is free, searchable, and built to be skimmed when you're in a hurry and read deeply when you're not.
Who it's for
Testers, obviously — from people breaking into QA to engineers leveling up their automation. But not only testers. Software is everyone's quality problem now. Developers writing their own tests, product managers who want to understand what "good coverage" means, anyone in the development process who's ever been unsure what a term meant or which tool to reach for — qa.codes is for you too. The goal is to make software testing understandable to anyone who touches software, not just the people with "QA" in their title.
Who's behind it
qa.codes is a solo project — built and maintained by one working quality engineer, drawn from years of hands-on testing experience across manual and automation work. That means it's opinionated where it should be, honest about tradeoffs, and shaped by what's actually useful on the job rather than what's easy to write. It also means it's always growing — new tools, references, and guides land regularly.
Before you ask
Why use qa.codes when AI tools can answer testing questions?
Because AI answers the question you already know to ask — qa.codes helps you find the questions, trust the answers, and see the whole landscape. An AI assistant is great when you know exactly what you're looking for, but it can be confidently wrong, work from outdated training data, and it can't show you what you didn't know to ask about. qa.codes is curated and kept current by someone who does the work: the tools are vetted, the references verified, and the roadmaps lay out paths you can follow. It's built to work alongside AI, not against it — which is also why there's a whole section on testing with AI.
Is it free?
Yes — everything on qa.codes is free, ad-free, and searchable. No paywall, no premium tier gating the useful parts. You can create an account to bookmark things and get notified when new content lands, but nothing essential is behind it.
Who maintains it, and how current is it?
qa.codes is built and maintained by one working quality engineer, and it's updated regularly — new tools, references, and guides land often. If you spot something missing, outdated, or wrong, — that feedback is genuinely how it gets better.
Found something missing, outdated, or wrong? That feedback makes qa.codes better.
Want to know when new tools, cheat sheets, and guides go live?