ISTQB Question Bank 461 to 500

What is the main difference between a walkthrough and an inspection?

• An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.
• An inspection has a trained leader, whilst a walkthrough has no leader.
• Authors are not present during inspections, whilst they are during walkthroughs.
• A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator.

Which of these activities provides the biggest potential cost saving from the use of CAST?

• Test management
• Test design
• Test execution
• Test planning

Which of the following is NOT true of incidents?

• Incident resolution is the responsibility of the author of the software under test.
• Incidents may be raised against user requirements.
• Incidents require investigation and/or correction.
• Incidents are raised when expected and actual results differ.

Which of the following characterizes the cost of faults?

• They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.
• They are easiest to find during system testing but the most expensive to fix then.
• Faults are cheapest to find in the early development phases but the most expensive to fix then.
• Although faults are most expensive to find during early development phases, they are cheapest to fix then.

Which one of the following statements, about capture-replay tools, is NOT correct?

• They are used to support multi-user testing.
• They are used to capture and animate user requirements.
• They are the most frequently purchased types of CAST tool.
• They capture aspects of user behaviour.

Which of the following is true of the V-model?

• It states that modules are tested against user requirements.
• It only models the testing phase.
• It specifies the test techniques to be used.
• It includes the verification of designs.

Error guessing:

• Supplements formal test design techniques.
• Can only be used in component, integration and system testing.
• Is only performed in user acceptance testing.
• Is not repeatable and should not be used.

In a system designed to work out the tax to be paid:

• �4800; �14000; �28000

• �5200; �5500; �28000

• �28001; �32000; �35000

• �5800; �28000; �32000

The oracle assumption:

• Is that there is some existing system against which test output may be checked.
• Is that the tester can routinely identify the correct outcome of a test.
• Is that the tester knows everything about the software under test.
• Is that the tests are reviewed by experienced testers.

In prioritising what to test, the most important objective is to:

• Find as many faults as possible.
• Test high risk areas.
• Obtain good test coverage.
• Test whatever is easiest to test.