What is the recommended approach to test case maintenance when the product changes?

• A. Delete all existing tests and rewrite from scratch.
• B. Update, retire, or add test cases to reflect new functionality and changed behavior; maintain traceability.
• C. Keep all tests unchanged regardless of changes.
• D. Only modify the test data, not the test cases.

Answer: (B)

When the product changes, the best approach is to update existing test cases to reflect the new functionality and the changed behavior, retire tests that no longer apply, and add new tests for the new features or edge cases, while preserving traceability from requirements through tests to defects. This keeps the suite aligned with current expectations and makes it clear why each test exists, which is essential for effective regression testing.

Updating tests ensures each one exercises the current behavior, including any new flows or altered outcomes. Retiring tests that no longer apply prevents false alarms and keeps the suite focused on relevant scenarios. Adding new tests captures new functionality and important edge cases that the old tests wouldn’t cover. Maintaining traceability means you can see which requirement or user story a test is validating, and how defects prompted its creation or modification, making it easier to assess impact when requirements shift.

Deleting all tests would throw away valuable history and coverage, and keeping everything unchanged ignores changes in functionality, risking missed regressions. Merely changing test data often isn’t enough because the test logic, steps, or expected results may need to evolve to reflect the new behavior.