Risk Assessment & Management Flashcards
7 cards from real Software Testing practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Risk Assessment & Management flashcards as text
A risk matrix shows a risk as 'Red.' According to typical risk-based testing strategy, what testing approach applies?
Answer: Apply thorough testing with multiple techniques and high coverage
Red (high) risks demand the most rigorous testing effort including multiple techniques, deep coverage, and early execution in the test cycle.
What is 'risk velocity' in software risk management?
Answer: How quickly a risk can escalate from low to critical if not addressed
Risk velocity measures how fast a risk can worsen or materialize, helping teams prioritize risks that can rapidly become severe.
During a risk review meeting, the team updates the probability of an existing risk from 'Low' to 'High' based on new information. This activity is called:
Answer: Risk reassessment
Risk reassessment is the periodic review process that updates risk ratings as new information becomes available during the project lifecycle.
Which practice helps reduce the risk of integration failures when multiple components are developed in parallel?
Answer: Continuous integration with automated build verification tests
Continuous integration detects integration defects immediately after each commit, dramatically reducing the probability and impact of late-stage integration failures.
A risk register entry shows Probability=0.4 and Impact=$50,000. What is the Expected Monetary Value (EMV) of this risk?
Answer: $20,000
EMV = Probability × Impact = 0.4 × $50,000 = $20,000, representing the weighted financial exposure of the risk.
Which statement correctly describes the difference between risk avoidance and risk reduction?
Answer: Avoidance eliminates the risk entirely; reduction lowers its probability or impact
Risk avoidance removes the cause of the risk completely (e.g., dropping a feature), while risk reduction takes actions that make the risk less likely or less harmful.
In a software testing context, which metric is MOST useful for tracking whether risk-based testing is reducing overall project risk over time?
Answer: Defect density in high-risk modules over successive test cycles
Tracking defect density in high-risk modules across test cycles shows whether testing and fixes are actually reducing risk in the areas that matter most.