Stage 2 · Lesson 7 of 8
Smoke, sanity and regression testing
A is a quick check that a new build works at all: the app starts, you can sign in, the main page loads. A sanity check confirms that one fix or small change did what it should. Regression testing checks that existing features still work after a change, because fixes and new code often break something nearby.
The regression suite grows every and soon becomes too slow to run by hand. That is the main reason teams automate. These stable, repeated regression checks are what you will automate first in the coming stages.
Common traprunning the whole regression pack by hand for every small change, or skipping regression entirely because "only one line changed".
A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock
Resources for this stage
Start with
- GuideFreeISTQB Certified Tester Foundation Level (CTFL) v4.0
ISTQB · Beginner
Chapter 4 of the free syllabus covers partitions, boundaries, decision tables and state transitions with worked examples
Practise
Keep handy
Also worth your time
A plain, proven checklist for titles, steps and expected results from one of the largest open bug trackers