Which two should be part of a testing plan involving a new technology? (Choose two.)

Question

Options

• AVolume and performance tests of software, hardware, and mobile devices
• BCost of equipment deployed in fifteen sites across a 500 square kilometer area
• CScenarios which require standard situations and test-out exception handling
• DEase of use for IT staff using the technology on an agile project to produce prototypes
• ETimeframe for break-fix of new infrastructure

• A
  6% (1)
• B
  13% (2)
• C
  75% (12)
• E
  6% (1)

Explanation

C and D belong in a testing plan because effective technology evaluation must cover both functional coverage (standard and edge-case scenarios in C) and human-factors assessment (how well IT staff can actually use the tool in practice, as in D). Option C ensures the test plan validates normal operation and gracefully handles unexpected inputs or failures - a core testing discipline. Option D captures usability and productivity fit, which is especially relevant in an agile prototyping context where rapid iteration depends on staff efficiency.

Why the distractors are wrong: A (volume/performance tests across devices) describes a load-testing strategy, not a testing plan component for evaluating new technology adoption. B (equipment cost across 15 sites) is a procurement and budget concern, not a testing activity. E (break-fix timeframe) is an operational SLA metric - it belongs in a support or change management plan, not a testing plan.

Memory tip: Think "What does a test plan actually test?" - it tests scenarios (C) and usability (D). Cost, timelines, and performance benchmarks across infrastructure are planning/operations concerns, not test plan elements.

No community discussion yet for this question.