Testing for performance problems
Hiring a contractor after a key test analyst quits
Procuring extra test environments in case one fails during testing
Performing a project retrospective using test results
Failure of a component vendor to conduct adequate component testing
Calculation of excessive late-payment penalties for invoices
On-time payment of all invoices for international vendors
Calculation of risk priority using likelihood and impact
Severity and priority
Functionality, reliability, usability, efficiency, maintainability and portability
Loss of a key contributor on the test team
Loss of a key contributor on the development team
A tester can provide input on the likelihood of a risk item.
A developer can provide input on the impact of a risk item.
A business analysis can provide input on the likelihood of a risk item.
A help desk staffer can provide input on the impact of a risk item.
You perform a risk analysis on the final requirements specification and subsequently receive a draft design specification.
A tester leaves after test design is complete, and you hire a new tester to replace her.
The development manager hires two additional programmers after the quality risk analysis is complete.
You perform a risk analysis on the final requirements specification and then that document is placed under formal configuration management.
Reduce the number of supported PC configurations
Assign more testers to cover compatibility that testers to cover functionality
Analyze the number of defects found that relate to this risk item
Plan to test the most common PC configuration
It is the project team's first application of risk-based testing.
The system under test is both complex and safety critical.
The system under test is a financial system.
Minimizing the amount of documentation is a key concern.
A strategy for regression testing
A list of advance amount boundary values
A description of intercase dependencies
A logical collection of test cases
In the test design specifications, explain the alternate approach planned for this project and how to set up the test configurations.
In the test procedure specifications, explain which test cases shhould be run against which configurations.
In the master test plan, explain the alternate approach planned for this project and why this approach is sufficient.
In the test item transmittal report, explain the alternate approach planned for this project and which test items ere tested against which configuration.
1. The approach section should describe how to test the integration of the thermostat with other parts of HVAC system.
1. The schedule section should describe when integration testing should start and when system testing should start.
1. The environmental needs section should address who is responsible for each level of testing.
1. The test items section should describe the equipment required for each level of testing.
1. The test deliverables section should describe results reporting for each level of testing.
Write a separate test plan for this level of testing.
List the feature that prevents excessive cycling as a feature to be tested.
Detail all of the requirements of the programmable thermostat in the introduction of the test plan.
Include a fully functioning compressor as one of the test items.
You would expect to find exactly 20 more defects before the end of system test.
You have omitted tests for at least one critical quality risk category.
You needed a test team of at least three testers for optimum testing.
You have found roughly the number of defects you would expect to find during system test.
Do not update the system test plan until the final version of the design specification is available.
Produce a draft update of the system test plan based on this version of the design specification
Check this version of the design specification for inconsistencies with the requirements specification
Participate in the final review of the design specification but not any preliminary reviews of the design specification
Review the quality risk analysis to see if the design specification has identified additional risk items
Counting the number of defects found and the number of defects resolved.
Counting the number of test cases passed and the number of test cases failed.
Counting the number of requirements that work properly and the number of requirements with known defects
Counting the number of tested risk items without known defects and the number of tested risk items with known defects
Redesign the fuel efficiency tests
Revise the quality risk analysis
Modify the test environment to gather more detailed actual results
Check for consistency in tested fuel mixtures
Report fuel efficiency as apparently unchanged
Revise all cash advance test cases to test with only one credit card.
Review all reports filed subsequently and close any such duplicate defect reports before assignment to development.
Change the requirements to delete support for American Express card.
Have testers check for similar problems with other cards and report their findings in defect reports.
Finding a bug during testing
Training developers in secure coding practices
Designing test cases
Fixing a customer-detected bug
Selection of an improper test partner
Communication problems created by time zone differences
Insufficient skills in some of the test team members
Inconsistent test processes across the testing locations