5.3 Test Monitoring & Control

Explanation
Metrics should be collected during and at the end of a test level in order to assess the effectiveness of the testing with respect to the objectives, the adequacy of the test objectives for that test level, and the adequacy of the test approaches taken. This means that all three statements (i, ii, iii) are correct. Collecting metrics allows for an evaluation of whether the testing was effective in achieving its objectives, whether the test objectives were appropriate for that specific test level, and whether the test approaches taken were sufficient.

Explanation
The correct answer is vi, iii, ii. This is because common test metrics typically include the number of testers involved in the testing process (vi), the measure of test case conditions (iii), and the number of test conditions to write (ii). These metrics help in assessing the progress and effectiveness of the testing efforts, as well as identifying any potential issues or areas for improvement.

Explanation
Test monitoring is not used to provide progress against exit criteria. Test monitoring is used to track and measure the progress of testing activities, provide feedback to stakeholders, and provide visibility into the status of test activities. However, progress against exit criteria is typically evaluated during the test closure phase or at the end of the testing process to determine if the testing objectives have been met.

Explanation
Test reporting is concerned with summarizing information about the testing endeavor, including the level of confidence in the software, outstanding risks, and economic benefit of continued testing. However, an assessment of defects resolved is not a part of test reporting. This activity falls under defect tracking and management, where defects are identified, logged, and tracked until they are resolved. Test reporting focuses on providing an overall summary of the testing process and its outcomes, rather than specifically assessing resolved defects.