Which of the following best suggests the need for maintenance testing?

Question

Options

• AFailures found in alpha testing
• BThe initial release of the software
• CChanging requirements during pre-deployment activities
• DAdding a new feature to an existing system

• B
  4% (1)
• D
  96% (24)

Explanation

Maintenance testing is triggered by modifications to an already-deployed, operational system - and adding a new feature to an existing system (D) is precisely that scenario, requiring testing of both the new functionality and regression testing to confirm nothing existing was broken.

Why the distractors fail:

• A - Failures in alpha testing prompt fixes within the active development cycle, not maintenance testing, which only applies post-deployment.
• B - The initial release hasn't been deployed yet; testing here belongs to system or acceptance testing phases, not maintenance.
• C - Changing requirements during pre-deployment still falls within the development lifecycle - maintenance testing begins only after the system is live in production.

Memory tip: Anchor the word "maintenance" to "something already built and running." If the system is already in production and you touch it - patch, update, new feature - that triggers maintenance testing. If it hasn't shipped yet, it's not maintenance.

No community discussion yet for this question.