There is a debate in your organization about who can close a defect report The developers think they should be able to reject and close defects without any further steps The testers are not happy with this approach as they are afraid the rejections may go undetected and the developers may close something without understanding the real problem How can this problem be rectified7

• A. Only testers should be allowed to close defect reports
• B. Closure should only occur when a defect is fixed and tested
• C. No one should close a defect report until the release is completed and the product is successfully deployed to production
• D. Only management should be allowed to close defect reports

At what testing level do the test management activities Include coordinating with end users7

• A. Component testing
• B. Component Integration testing
• C. Acceptance testing
• D. System testing

You have been assigned t o a project that has a very tight schedule. In fact, given your first analysis you do not think the planned test execution can be completed within the schedule There is no time allowed for defect fixing or for repeating tests. Regression testing has been left out of the planning entirely There is no time to develop test automation. The team has agreed that this Is not the way to run a project, yet they are stuck with the current schedule Given this information what is the best way to proceed with the testing to try to meet the deadline with the best outcome1?

• A. Continue with the current plan but highlight to the project manager that either the deadline will be missed or the testing will not be done
• B. Review the personnel plan and get more resources onto the test team
• C. Conduct a quality risk analysis and prioritize the testing based on risk so the highest risk items are tested first
• D. Develop a test automation plan so that automation can be started now

Your team has decided that they will build their own test management tool This will allow them to link the requirements and test cases together providing full traceability It will also allow them to create fully customized reporting and color-coded dashboards They have estimated the time required to create the new tool and the cost These fit within the project schedule and budget What other consideration should be taken before this decision is made?

• A. Reduction of manual repetitive testing
• B. Maintenance costs
• C. Relative benefits to your vendors
• D. Licensing fees to other parts of the organization

You have been looking at the actual vs expected defects in one high risk area of the software The actual is much higher than the expected value What should you do?

• A. Reassess the risk with a higher likelihood number
• B. Concentrate more testing in the area because the risk is clearly higher
• C. Reassess the risk with a higher impact number
• D. Concentrate less testing in the area because the defects are already found