Software testing foundations
What testing is for, the words the profession uses, and the four kinds of work that hide behind the one job title.
Every field has a handful of words that mean something precise to the people inside it and something vaguer to everyone else. Regression, acceptance, coverage and flaky all do real work in a stand-up, and all four are routinely used to mean four different things around the same table. The fastest way to stop being new is to learn what your colleagues actually mean, which is a smaller job than it sounds.
The second thing worth knowing early is that “testing” is not one activity. The clearest map of it is still the agile testing quadrants, drawn by Brian Marick and popularised by Lisa Crispin and Janet Gregory. It splits the work along two axes: whether a test is written in the language of the business or the language of the code, and whether it exists to help the team build the thing or to find out what is wrong with the thing they built.
The reason this matters on day one is that automation only reaches part of the picture. Q1 and Q2 automate well and should be automated. Q4 is automatable but specialised. Q3 — exploratory work, usability, the judgement call that something is technically correct and still wrong — is not automatable at all, and a team that measures itself only on automated pass rates has quietly decided that quadrant does not count.
The ISTQB syllabus is a free, orderly tour of the terms your colleagues use, and reading it is worth an afternoon. Sitting the exam is a hiring signal in some markets and worth nothing in others, and nobody's test suite has ever improved because of it. Read the glossary; skip the flashcards.
The shared vocabulary
4 entriesRead one of these properly rather than four of them partly.
-
ISTQB Glossary
StandardEvery term in the profession with an agreed definition, searchable, free. When a colleague says “smoke test” and you are not certain you mean the same thing, this settles it in ten seconds. More useful day to day than the syllabus it comes from.
glossary.istqb.org -
ISTQB Foundation syllabus
StandardThe orderly version of the same material: what testing is for, how it fits a development lifecycle, the standard techniques and where they apply. Free to download in dozens of languages. Treat it as a map of the territory rather than as a set of instructions.
www.istqb.org -
James Bach and Michael Bolton's methodology, and the strongest available counterweight to treating testing as a checklist. Its central claim — that testing is an investigation performed by a skilled human, and that anything a machine does is checking — will change how you read every other resource on this page.
rapid-software-testing.com -
Bach's one-page model of what to think about when deciding how to test something: project environment, product elements, quality criteria. Print it. It is the fastest cure for staring at a new feature with no idea where to begin.
www.satisfice.com
Learning the mechanics
3 entriesFree, structured, and made by people who do the work.
-
Free video courses from working practitioners, from first principles through to specific frameworks, with exercises. The one place to send someone who asks “how do I get into automation” and wants a path rather than a link.
testautomationu.applitools.com -
Google Testing Blog
EssayShort, opinionated posts from a team that tests at a scale almost nobody else has. The “Testing on the Toilet” series is one page each and is the best five-minute read in the field; the posts on test sizes and on flakiness are cited everywhere else on this site.
testing.googleblog.com -
MDN: learn web development
Official docsNot a testing resource, and on this page on purpose. Automation is reading other people's HTML for a living. An hour on what a form control, a label and an ARIA role actually are pays for itself the first time a locator breaks and you can see why.
developer.mozilla.org
What to take away
- Learn the words first.Most disagreements about testing are two people using one word for two things. The glossary is free and takes an afternoon.
- Automation covers two quadrants well.If your only measure of quality is a pass rate, you have decided exploratory testing does not count.
- Pick one philosophy and read it properly.ISTQB and Rapid Software Testing disagree with each other. Reading either one closely beats skimming both.
Reading is the slow way to learn how a suite behaves. Record one against your own app, free, and watch what the report says.