Risk analysis for testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the risk level based on impact.

Testing Fundamentals

risk_level = 'High' if impact [1] 7 else 'Low'

Drag options to blanks, or click blank then click option'

A<

B==

C>=

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>=' causes the risk level to be set incorrectly.

Using '==' only checks for exactly 7, missing higher impacts.

The risk level is 'High' when the impact is greater than or equal to 7.

2fill in blank

medium

Complete the code to calculate risk priority by multiplying probability and impact.

Testing Fundamentals

risk_priority = probability [1] impact

Drag options to blanks, or click blank then click option'

A*

B/

C-

D+

Attempts:

3 left

💡 Hint

Common Mistakes

Using '+' adds values but does not reflect combined risk properly.

Using '/' or '-' changes the meaning and results in incorrect priority.

Risk priority is calculated by multiplying probability and impact to reflect combined effect.

3fill in blank

hard

Fix the error in the risk assessment function to return correct risk level.

Testing Fundamentals

def assess_risk(probability, impact):
    if probability [1] 0.7 and impact >= 7:
        return 'High'
    else:
        return 'Low'

Drag options to blanks, or click blank then click option'

A>=

B<

C<=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<=' reverses the logic and causes wrong risk classification.

Using '==' only matches exactly 0.7, missing higher probabilities.

The function checks if probability is greater than or equal to 0.7 to assess high risk.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps test cases to risk levels based on priority.

Testing Fundamentals

risk_map = {test_case: 'High' if priority [1] 50 else 'Low' for test_case, priority in test_priorities.items() if priority [2] 10}

Drag options to blanks, or click blank then click option'

A>=

B<

C>

D<=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>=' in the first blank reverses risk assignment.

Using '>=' instead of '<' in the second blank includes wrong priorities.

The comprehension assigns 'High' risk if priority is at least 50 and includes only priorities less than 10 in the dictionary.

5fill in blank

hard

Fill all three blanks to create a filtered dictionary of test cases with risk priority above threshold and label them.

Testing Fundamentals

filtered_risks = { [1]: priority for [2], priority in risks.items() if priority [3] threshold }

Drag options to blanks, or click blank then click option'

Atest_case

Btest

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' in the last blank filters the wrong priorities.

Mixing variable names causes confusion and errors.

The dictionary comprehension uses 'test_case' as key, 'test_case' as loop variable, and filters priorities greater than threshold.

Practice

1. What is the main purpose of risk analysis in software testing?

easy

A. To write code faster without testing

B. To identify which parts of the software need testing first based on potential problems

C. To create user manuals for the software

D. To design the software's user interface

Solution

1. Step 1: Understand risk analysis goal

   Risk analysis helps testers find which parts of software might cause big problems.

2. Step 2: Connect goal to testing order

   Testing starts with high-risk areas to catch serious issues early.

3. Final Answer:

   To identify which parts of the software need testing first based on potential problems -> Option B

4. Quick Check:

   Risk analysis = prioritize testing by risk [OK]

Hint: Risk analysis = test high-risk parts first [OK]

Common Mistakes:

• Thinking risk analysis is about coding speed
• Confusing risk analysis with documentation
• Believing risk analysis designs UI

2. Which of the following is a correct way to describe risk in testing?

easy

A. Risk is the chance that a feature will be easy to use

B. Risk is how fast the software runs

C. Risk is the likelihood and impact of a problem occurring in the software

D. Risk means the software will never have bugs

Solution

1. Step 1: Define risk in testing context

   Risk means how likely a problem is and how bad its effect would be.

2. Step 2: Match definition to options

   Risk is the likelihood and impact of a problem occurring in the software correctly states risk as likelihood and impact of problems.

3. Final Answer:

   Risk is the likelihood and impact of a problem occurring in the software -> Option C

4. Quick Check:

   Risk = likelihood + impact [OK]

Hint: Risk = chance x impact of problem [OK]

Common Mistakes:

• Confusing risk with software speed
• Thinking risk means no bugs
• Mixing risk with usability

3. Given the following risk scores for features, which feature should be tested first?
Feature A: Impact=5, Likelihood=2
Feature B: Impact=3, Likelihood=4
Feature C: Impact=4, Likelihood=4
Feature D: Impact=2, Likelihood=5

medium

A. Feature C

B. Feature B

C. Feature A

D. Feature D

Solution

1. Step 1: Calculate risk scores

   Multiply impact and likelihood for each feature:
   Feature A: 5x2=10
   Feature B: 3x4=12
   Feature C: 4x4=16
   Feature D: 2x5=10

2. Step 2: Identify highest risk

   Feature C has the highest risk score (16), so test it first.

3. Final Answer:

   Feature C -> Option A

4. Quick Check:

   Highest risk = Feature C (16) [OK]

Hint: Test feature with highest impact x likelihood first [OK]

Common Mistakes:

• Choosing feature with highest impact only
• Choosing feature with highest likelihood only
• Adding instead of multiplying impact and likelihood

4. A tester assigned risk scores as Impact=3 and Likelihood=5 for a feature. Later, they realize the impact should be 5, but they forgot to update the risk score. What is the error in their risk analysis?

medium

A. Incorrect calculation of risk score due to outdated impact value

B. Wrong likelihood value used

C. Risk analysis does not require impact values

D. Risk score should be ignored if updated values are missing

Solution

1. Step 1: Identify the mistake in risk scoring

   The tester used an old impact value (3) instead of the correct one (5).

2. Step 2: Understand effect on risk score

   This causes the risk score to be too low, leading to wrong testing priority.

3. Final Answer:

   Incorrect calculation of risk score due to outdated impact value -> Option A

4. Quick Check:

   Outdated impact causes wrong risk score [OK]

Hint: Always update impact and likelihood before scoring [OK]

Common Mistakes:

• Ignoring impact changes
• Assuming likelihood was wrong
• Thinking risk score can be skipped

5. You have three features with these risk values:
Feature X: Impact=4, Likelihood=3
Feature Y: Impact=5, Likelihood=2
Feature Z: Impact=3, Likelihood=5
If testing time is limited and you can only test two features, which two should you pick to maximize risk coverage?

hard

A. Feature Y and Feature Z

B. Feature X and Feature Y

C. Feature X and Feature Y and Feature Z

D. Feature X and Feature Z

Solution

1. Step 1: Calculate risk scores for all features

   Feature X: 4x3=12
   Feature Y: 5x2=10
   Feature Z: 3x5=15

2. Step 2: Select two features with highest combined risk

   Feature Z (15) and Feature X (12) together cover 27 risk points, higher than other pairs.

3. Final Answer:

   Feature X and Feature Z -> Option D

4. Quick Check:

   Pick top two risk scores for best coverage [OK]

Hint: Pick two features with highest risk scores combined [OK]

Common Mistakes:

• Choosing features with highest impact only
• Selecting features with lowest risk
• Trying to test all three when time is limited