In an Agile context, defects are often fixed without writing a formal defect report. However, there are some conditions where it is good practice
to write a defect report, even in an Agile context.
When is a defect report typically not written in an Agile context?
Answer : D
Management is sceptical regarding the budget request (25,000) for the next testing project. You are asked for a cost-benefit calculation. Based on historical data from several projects, you have come up with the following numbers:
Average prevention cost per defect: 200
Average cost of detection per defect: 400
Average cost of internal failure: 150
Average cost of external failure: 2,500
Expected number of defects to be found in this project during testing: 50
What is the result for the expected cost-benefit calculation for the upcoming project?
Answer : C
Study the following characteristics:
Avoid re-inventing the wheel
Pool on experiences from earlier projects
They prompt thought in areas that are sometimes forgotten
Often used when compliance to specific standards is relevant
To which risk identification technique do these characteristics relate?
Answer : D
A project has been running for a few months and the team does not seem to be making progress in their test approach. The team also lacks drive and enthusiasm and is sometimes seen to be performing their tasks too slowly. You have been asked to recruit an extra person into the team. In addition to introducing the new team member, you have decided to raise motivation.
Which of the actions listed below would most likely result in the opposite, a de-motivation of the team?
Answer : B
During which test planning task are the test design techniques to be applied during the project, identified and selected?
Answer : C
The diagram below shows an incomplete defect management process, where three states (states X, Y and Z) have yet to be named appropriately.
Which of the following labels would correctly complete the process?
Answer : C
You have recently been employed as a test manager for a software company producing Human Resource (HR) systems, namely Payroll,
Personnel and Recruitment systems. The company is relatively new and wants to make a major impact in the market by producing a world-class
enterprise HR product. They will work with a panel of potential customers throughout its development. It's important that the development and
test approach are flexible since many changes are expected throughout the development of the new HR software products. A test team has
been set up with persons who have a lot of HR domain knowledge. You have been asked to write a test strategy for the project and have chosen
to implement a flexible and change-related reactive test strategy.
Which of the following would be an essential part of your test approach?
Answer : D