Una strategia di testing definisce come un progetto assicura la qualità — cosa testare, a quali livelli, quanto, con quali strumenti e processi. Una buona strategia bilancia la completezza con il costo, concentrando lo sforzo di testing dove fornisce il massimo valore.
Elementi di una strategia di testing
✓ 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
