Not a loyalty test — a scheduling one. Scripted proves the behaviour you already know to check; exploratory finds what nobody specified. Here's which to reach for, when, and how to blend them in one cycle.
Not rivals fighting over the same budget — different jobs. Automation guards what you already know; manual testing judges what you don't. Draw the line wrong and you get a brittle suite and the important bugs still escaping.
Retesting confirms a fix works; regression checks the fix didn't break anything else. Plan them as one task and the 'we fixed it' build ships a brand-new bug. Here's the split, and how they combine after a fix.
Smoke asks 'is this build worth testing?'; sanity asks 'did this change work?' Both are quick gut-checks at different moments. Use them as gates before the real testing — and stop wasting a full pass on a dead build.
The three 'box' terms are interview trivia until you use them right: they describe how much of the code you can see when designing a test, which decides what you'll catch. Most functional QA is quietly grey-box — here's why.
Test cases that get read are short, scannable, and written for the person who has to act on them. Here is the format I use.
A field-tested approach for testing a story when the acceptance criteria are vague, missing, or contradictory.
How to scope a regression pass to the change in front of you instead of re-running the entire suite by hand.
A bug report exists to get the bug fixed. Specific title, minimal repro steps, explicit expected-vs-actual, evidence, and environment — the format that prevents "can't reproduce".
Six months from your first if-statement to your first paid automation contract — if you focus. Here's the path I'd take if I were starting today.
What automation replaced was regression checks — running the same path repeatedly. What it didn't replace, and can't replace, is human intuition trying to break a product.