Test Management Quiz

Risk-based testing prioritizes testing high-risk areas because failures in these areas would have the most severe impact on the business or users. While finding faults and obtaining good coverage are important goals, they are means to an end. Testing 'whatever is easiest' provides false confidence and is poor practice.

In the standard software testing lifecycle, test cases are created during the test specification phase. Test planning defines the overall approach, test configuration sets up the environment, and test recording captures execution results. Test specification is where detailed test cases and procedures are documented.

IEEE 829 Test Plan includes test items, features to be tested, approach, resources, schedule, test environment properties, and risks. 'Quality plans' are separate documents focused on quality assurance processes, not specifically part of the Test Plan document itself. The Test Plan does include 'what is not to be tested' as a specific section.

Stress testing is a type of system or performance testing, not unit testing. Equivalence partitioning, syntax testing, and MC/DC are all standard techniques used at the unit testing level.

Testing is complete when the predetermined exit criteria are met, typically expressed as a required level of confidence in the system's quality. Time constraints (A) are arbitrary, finding zero faults is impossible (C), and user perception (D) is unpredictable. Option B reflects proper test completion based on defined acceptance criteria and risk mitigation.

Test managers should report deviations, raise incidents, and sign off for release based on quality criteria. However, blindly reallocating resources to meet original plans when circumstances have changed is poor management practice. Plans should adapt to reality, not the other way around. Forcing resource reallocation to meet outdated dates can compromise quality.