Independent testing is usually cheaper than testing your own work.
Independent testing is more effective at finding defects.
Independent testers should determine the processes and methodologies used.
Independent testers are dispassionate about whether the project succeeds or fails.
Develop system requirements, design specifications and usage models.
Handle all test automation duties.
Keep tests and test coverage hidden from programmers.
Gather and report test progress metrics.
A test manager manages a collection of test leaders.
A test manager is the leader of a test team or teams.
A test manager gets paid more than a test leader.
A test manager reports to a test leader.
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 programmers 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.
Geographical separation of tester and programmers.
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.
Test team training
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.
A group of test activities that are organized together.
One or more test design specification documents.
A test type.
An ISTQB certification.
Percentage of test cases written.
Number of test environments remaining to be configured.
Number of defects found and fixed.
Percentage of requirements for which a test has been written.
The remaining 15 defects should be confirmation tested prior to release.
The remaining 10% of test cases should be run prior to release.
The system is now ready for release with no further testing or development effort.
The programmers should focus their attention on fixing the remaining known defects prior to release.
Summary of activities
Test documentation management
The arrival of a more-reliable competing product on the market.
Delivery of an incomplete test release to the first cycle of system test.
An excessively high number of defect fixes fail during re-testing.
Failure to accept allowed credit cards.
Difficulty of fixing related problems in code
The harm that might result to the user
The price for which the software is sold
The technical staff in the meeting
Unexpected illness of a key team member
Excessively slow transaction-processing time
Data corruption under network congestion
Failure to handle a key use case
Determine the extent of testing required for the product risks and the mitigation and contingency actions required for the project risks.
Obtain the resources needed to completely cover each product risk with tests and transfer responsibility for the project risks to the project manager.
Execute sufficient tests for the product risks, based on the likelihood and impact of each product risk and execute mitigation actions for all project risks.
No further risk management action is required at the test planning stage.
Control of the test project
The test object
A single test item
A potential negative outcome
Item pass/fail criteria
A bug report
A defect report
An incident report
A test summary report
To identify new risks to system quality.
To locate defect clusters in product subsystems.
To check risk coverage by tests.
To measure exploratory testing.