| Aspect | Explanation |
|---|---|
| Purpose | Testing is the key quality risk mitigation activity to reduce the likelihood of failures. |
| Other Mitigation Options | Contingency planning (e.g., workarounds), risk transfer (e.g., to vendor), risk acceptance. |
| Testing Proportional to Risk | Higher risk = early, rigorous testing; Lower risk = later, lighter testing. |
| Contextual Factors for Test Approach | |
| - Test Items | Different parts of the system may have different risk levels; tailor testing effort accordingly. |
| - Quality Characteristics | Match risks to quality attributes and test types (e.g., usability, security). |
| - Test Levels and Types | Static or dynamic testing, unit vs system level – based on what suits the risk. |
| - SDLC Considerations | Entry criteria and timing vary across development models (e.g., Agile vs. V-model). |
| - Test Team Capability | Assign experienced testers to high-risk items. |
| - Regulatory Needs | Standards (e.g., IEC 61508) may prescribe specific test techniques or coverage. |
| Impact on Quality Control | Risk level influences test reviews, independence, and extent of regression testing. |
| Test Monitoring & Control | Track residual risk throughout testing; helps guide release decisions. |
| Test Prioritization Approaches | |
| - Depth-First | Prioritize and execute tests covering highest risk first. |
| - Breadth-First | Ensure at least one test per risk item is run early for an overall quality view. |
| - Hybrid | Start with depth-first, then breadth-first as time runs out. |
| Result if Time Runs Out | Not all planned tests may run – risk-based prioritization ensures critical areas tested |
Q1. A banking application has a critical login component with high security risks. What test approach should the test manager use?
A. Breadth-first B. Depth-first ✅ C. Risk acceptance D. Contingency planning
Explanation: Depth-first ensures the highest risk area (login/security) is tested first.
Q2. Your test team is less experienced. How should this influence your risk mitigation strategy?
A. Assign high-risk tests to junior testers B. Delay testing until training is complete C. Reassign high-risk testing to the most experienced testers ✅ D. Avoid testing high-risk areas
Q3. In a regulated medical device project, which factor must influence your testing?
A. Tester's opinion B. Project manager’s budget limits C. Regulatory requirements (e.g., IEC 61508) ✅ D. Developers' preferences
Q4. A test manager reports residual risk levels weekly. This practice supports:
A. Team morale B. Random test execution C. Release decision-making ✅ D. Cost estimation
Q5. When using a hybrid approach to risk-based testing, which sequence is correct?
A. Breadth-first only B. Start with random tests, then move to risk tests C. Start with depth-first, then switch to breadth-first ✅ D. Skip depth-first if time is limited
Exam-Style Test Simulation Practice (5 Questions)
Q1. What is the main goal of risk-based testing? A. Minimize cost of test automation B. Maximize code coverage C. Mitigate quality risks through targeted testing ✅ D. Execute all possible test cases
Q2. During which test phase should the most qualified testers be assigned to high-risk areas? A. Test planning ✅ B. Test execution C. Defect triage D. Requirement review
Q3. What is the benefit of tracking residual risk during test execution? A. Improves unit test code B. Ensures all features are tested C. Supports informed decision-making for release ✅ D. Removes the need for documentation
Q4. If only one test per risk is prioritized initially, what approach is being followed? A. Regression-first B. Risk acceptance C. Depth-first D. Breadth-first ✅
Q5. Why might testing not cover all planned test cases? A. Budget limitations B. Time constraints – risk-based prioritization ensures critical areas are still covered ✅ C. Lack of test data D. Developer’s approval is pending
No comments:
Post a Comment