Comprehensive testing requires running test scripts for the specific change (A), verifying existing functionality still works (B), and testing negative/boundary conditions (C). All three aspects together ensure quality. Only doing one or two types leaves gaps in test coverage and can miss regressions or edge cases.