Roadmap › Test Automation — Selenium, Playwright, API and BDD with C# › Module: Testing Fundamentals
Lessons in this course (10)
1. Testing types, terms and what to automate
Basic★ Must knowLesson 1 of 10
| Term | Meaning |
|---|---|
| Functional vs non-functional | What it does vs how well (performance, security, usability) |
| Smoke | Few critical checks — is the build alive? |
| Sanity | Quick check of one changed area |
| Regression | Re-run existing tests to catch side effects of changes — the main candidate for automation |
| Black box / white box | Without / with knowledge of the code |
| Verification vs validation | Built right (spec) vs built the right thing (user need) |
| Severity vs priority | Impact on the system vs urgency to fix |
Automate: repetitive regression, smoke, data-driven cases, API contracts, cross-browser checks, stable features. Keep manual: exploratory testing, usability/look-and-feel, one-off checks, features still changing daily.
Test case design techniques: equivalence partitioning, boundary value analysis (age 17/18/99/100), decision tables, state transition, pairwise.