Bug severity vs priority in Testing Fundamentals - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to assign the correct bug severity level.

Testing Fundamentals

bug_severity = "[1]"  # This bug causes the system to crash

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

ALow

BTrivial

CMinor

DCritical

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'Low' or 'Minor' for a crash bug.

The bug causes the system to crash, so its severity is Critical.

2fill in blank

medium

Complete the code to assign the correct bug priority level.

Testing Fundamentals

bug_priority = "[1]"  # This bug should be fixed before the next release

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

ALow

BMedium

CHigh

DDeferred

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing priority with severity.

The bug must be fixed before the next release, so its priority is High.

3fill in blank

hard

Fix the error in the code to correctly check if a bug is both critical and high priority.

Testing Fundamentals

if bug_severity == "[1]" and bug_priority == "High":
    print("Fix immediately")

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

ACritical

BHigh

CLow

DMedium

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'High' for severity instead of priority.

The severity must be checked as Critical to match the condition for immediate fix.

4fill in blank

hard

Fill both blanks to create a dictionary mapping bug severity to priority.

Testing Fundamentals

bug_map = {"Critical": "[1]", "Minor": "[2]"}

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

AHigh

BLow

CMedium

DDeferred

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up priority levels for severities.

Critical bugs usually have High priority, while Minor bugs often have Low priority.

5fill in blank

hard

Fill all three blanks to filter bugs with severity Critical and priority High.

Testing Fundamentals

filtered_bugs = [bug for bug in bugs if bug['severity'] == '[1]' and bug['priority'] == '[2]' and bug['status'] == '[3]']

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

ACritical

BHigh

COpen

DClosed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Closed' status instead of 'Open'.

We filter bugs that are Critical severity, High priority, and currently Open to fix them first.

Practice

1. What does bug severity describe in software testing?

easy

A. How serious or harmful the bug is to the system

B. How quickly the bug should be fixed

C. Who reported the bug

D. The number of times the bug occurred

Solution

1. Step 1: Understand severity meaning

   Severity measures the impact or seriousness of a bug on the system's functionality or performance.

2. Step 2: Differentiate from priority

   Priority is about the order of fixing, not the impact itself.

3. Final Answer:

   How serious or harmful the bug is to the system -> Option A

4. Quick Check:

   Severity = Impact [OK]

Hint: Severity = impact level, priority = fix order [OK]

Common Mistakes:

• Confusing severity with priority
• Thinking severity is about who reports the bug
• Mixing severity with bug frequency

2. Which of the following correctly describes priority in bug tracking?

easy

A. The order in which the bug should be fixed

B. The severity level of the bug

C. The number of users affected by the bug

D. The type of bug found

Solution

1. Step 1: Define priority

   Priority tells the team how soon a bug should be fixed based on business needs or deadlines.

2. Step 2: Compare with severity

   Severity is about impact, priority is about timing and importance for fixing.

3. Final Answer:

   The order in which the bug should be fixed -> Option A

4. Quick Check:

   Priority = Fix order [OK]

Hint: Priority = fix order, not impact [OK]

Common Mistakes:

• Mixing priority with severity
• Assuming priority depends on bug type
• Confusing priority with user count

3. A bug causes the application to crash for all users, but the fix can wait until the next release. What is the likely severity and priority?

medium

A. High severity, high priority

B. Low severity, high priority

C. High severity, low priority

D. Low severity, low priority

Solution

1. Step 1: Assess severity

   Application crash affects all users, so severity is high because it impacts functionality seriously.

2. Step 2: Assess priority

   Fix can wait until next release, so priority is low because it is not urgent to fix immediately.

3. Final Answer:

   High severity, low priority -> Option C

4. Quick Check:

   Crash = High severity, fix delay = Low priority [OK]

Hint: Crash = high severity; fix timing = priority [OK]

Common Mistakes:

• Assuming crash always means high priority
• Confusing severity with priority urgency
• Ignoring fix timing in priority

4. A tester marked a cosmetic UI bug as 'High Priority' but 'Low Severity'. What is the best correction?

medium

A. Change priority to High, keep severity High

B. Change priority to Low, keep severity Low

C. Change severity to Low, keep priority High

D. Change severity to High, keep priority High

Solution

1. Step 1: Understand cosmetic bug impact

   Cosmetic bugs usually have low severity because they don't affect functionality.

2. Step 2: Adjust priority based on impact

   Since cosmetic bugs are not urgent, priority should also be low to avoid wasting resources.

3. Final Answer:

   Change priority to Low, keep severity Low -> Option B

4. Quick Check:

   Cosmetic bug = Low severity & priority [OK]

Hint: Cosmetic bugs usually low priority and severity [OK]

Common Mistakes:

• Setting high priority for cosmetic bugs
• Confusing severity with priority urgency
• Ignoring bug impact on functionality

5. A security vulnerability allows data leaks but affects only a small user group. The business wants it fixed quickly. How should severity and priority be set?

hard

A. High severity, Low priority

B. Low severity, High priority

C. Low severity, Low priority

D. High severity, High priority

Solution

1. Step 1: Evaluate severity of security vulnerability

   Security issues causing data leaks are serious, so severity is high regardless of user count.

2. Step 2: Consider business urgency for fix

   Business wants quick fix, so priority must be high to address the risk fast.

3. Final Answer:

   High severity, High priority -> Option D

4. Quick Check:

   Security risk = High severity & priority [OK]

Hint: Security bugs = always high severity and priority [OK]

Common Mistakes:

• Lowering severity due to small user impact
• Ignoring business urgency in priority
• Confusing severity with priority