Your company has adopted an Agile methodology. Defect reports are not raised for all bugs found during the testing of individual stories, but continue to be raised in some circumstances, e.g., when the fix cannot be made immediately, or would involve another team. The teams would like better data to use for assessing the quality of their work. The list below shows five items that are currently not captured on defect reports.
Which TWO of these items will be MOST useful for assessing the quality of a product increment?

• A. The level of testing which found the defect
• B. The test environment in which the defect was found
• C. The quality characteristic / sub-characteristic that is affected
• D. The type of the defect from a defect taxonomy
• E. The user story to which the defect relates

You have done a comprehensive risk analysis. You have involved the appropriate people in assessing the risks and determining the likelihood and impact of those risks. You have been testing for three months and have been able to mitigate 75% of the high risk items. You have two weeks left in testing and you now do not expect to be able to complete all the items on the high-risk mitigation list, never mind any from the medium or low-risk lists.
What is the most effective action you should take? [3]

• A. Use a random selection algorithm to pick tests from the high, medium, and low risk mitigation lists - thereby ensuring that each risk list has some mitigation.
• B. Present your risk mitigation progress and project status to the project's stakeholders, and request additional time or assistance in re-prioritizing the remaining high-risk items.
• C. Retest the highest risk areas to ensure no regressions have occurred.
• D. Concentrate testing in areas that have already found numerous problems.

You are reviewing the project's traceability matrix after the first cycle of testing. You have discovered that new requirements have been introduced and others have changed.
What should you do? [2]

• A. Re-assess the test coverage.
• B. Assign the new requirements to a maintenance release, update the test documentation for the changed requirements.
• C. Update the "lessons learned" document to avoid future issues similar to this.
• D. Ask for more time and budget for testing.

How might test monitoring and reporting differ for a project using a SCRUM development model rather than a V-model?

• A. Reports are produced on a continuous basis with real-time dashboards and daily status updates
• B. Monitoring is more informal with less need for regular status reports
• C. Responsibility for test monitoring and reporting lies with the Product Owner, rather than the test manager
• D. A move to milestone-based reporting, with optional automated dashboards

Which of the following Is considered a heavyweight risk-based testing technique'

• A. Systematic software testing
• B. Pragmatic risk analysts
• C. Hazard analysis
• D. Brainstorming