O strategie de testare definește cum un proiect asigură calitatea — ce să testeze, la ce niveluri, cât de mult, cu ce instrumente și procese. O strategie bună echilibrează rigurozitatea cu costurile, concentrând efortul de testare acolo unde oferă cea mai mare valoare.
Elementele unei strategii de testare
✓ WHAT to test → critical functionality, risky/complex areas, core business logic
(prioritize by RISK and value — you can't test everything)
✓ LEVELS → the test pyramid: many unit, some integration, few E2E (balance coverage/cost)
✓ TYPES → functional + non-functional (performance, security) as needed
✓ TOOLS/frameworks → appropriate for the stack; CI integration
✓ PROCESS → when tests run (CI on every change), coverage expectations, who owns tests
✓ AUTOMATION vs manual → automate regression/repetitive; manual for exploratory/usability
