NEW
Font size
WorksheetsChapter 5 Test Management Part 1
Total questions: 10
Worksheet time: 10mins
What is a potential drawback of independent testing?
Independent testing is likely to find the same defects as developers.
Developers may lose a sense of responsibility for quality.
Independent testing may find more defects.
Independent testers may be too familiar with the system.
Which of the following is among the typical tasks of a test manager?
Develop system requirements, design specifications and usage models.
Handle all test automation duties.
Keep tests and test coverage hidden from developers.
Gather and report test progress metrics.
According to the ISTQB Glossary, what do we mean when we call someone a test manager?
A test manager manages a team of junior testers.
A test manager plans and controls testing activities.
A test manager sets up test environments.
A test manager creates a detailed test execution schedule.
What is the primary difference between the test plan, the test design specification and the test procedure specification?
The test plan describes one or more levels of testing, the test design specification identifies the associated high-level test cases and a test procedure specification describes the actions for executing a test.
The test plan is for managers, the test design specification is for developers and the test procedure specification is for testers who are automating tests.
The test plan is the least thorough, the test procedure specification is the most thorough and the test design specification is midway between the two.
The test plan is finished in the first third of the project, the test design specification is finished in the middle third of the project and the test procedure specification is finished in the last third of the project.
Which of the following factors is an influence on the test effort involved in most projects?
Geographical separation of tester and developers.
The departure of the test manager during the project.
The quality of the information used to develop the tests.
Unexpected long-term illness by a member of the project team.
A business domain expert has given advice and guidance about the way the testing should be carried out and a technology expert has recommended using a checklist of common types of defect. Which two test strategies are being used?
Analytical and Process compliant.
Reactive and Methodical.
Directed and Methodical.
Regression-averse and Analytical.
Consider the following exit criteria which might be found in a test plan:
I. No known customer-critical defects.
II. All interfaces between components tested.
III. 100% code coverage of all units.
IV. All specified requirements satisfied.
V. System functionality matches legacy system for all business rules.
Which of the following statements is true about whether these exit criteria belong in an acceptance test plan?
All statements belong in an acceptance test plan.
Only statement I belongs in an acceptance test plan.
Only statements I, II and V belong in an acceptance test plan.
Only statements I, IV and V belong in an acceptance test plan.
According to the ISTQB Glossary, what is a test approach?
The implementation of the test strategy for a specific project.
Documentation that expresses the generic requirements for testing one or more projects within an organization providing detail on how testing is to be performed.
Documentation describing the test objectives to be achieved and the means and the schedule for achieving them, organized to coordinate testing activities.
The set of interrelated activities comprising of test planning, test monitoring and control, test analysis, test design, test implementation, test execution and test completion.
There are five tests to be executed. A high-priority test has been scheduled as the third in the sequence of five, rather than the first. Which of the following would NOT be a good reason for this?
The high priority test has a logical dependency on the two tests run before it.
All tests are the same priority and this is the most efficient sequence.
The tests scheduled before it are more likely to pass so this will take less time and give feedback more quickly.
The first three tests have the same priority so it does not matter what order they are run in.
Exit criteria have been agreed at the start of the project, but it is now clear that they will not all be met before the release date next week. What should the test manager NOT say to those who want to release next week anyway?
These exit criteria were agreed for a very good reason, to avoid this situation. It is essential that all exit criteria are met before we release.
It is not my role to make that decision, so if you go ahead and release next week anyway, I will carefully monitor the effects and will report the results to high-level management.
Have all project stakeholders, business owners and the product owner been informed of the risks of releasing next week, and do they all understand and accept them? (Sign on this paper stating this.)
What are the most critical exit criteria, and can we get agreement from all stakeholders about which are absolutely necessary and which could be compromised this time?
