Bug severity vs priority in Testing Fundamentals - Test Execution Compared

Test Overview

This test checks if a bug tracking system correctly assigns and displays bug severity and priority levels. It verifies that severity and priority labels appear as expected when a bug is created.

Test Code - unittest

Testing Fundamentals

import unittest
from bug_tracker import Bug, BugTracker

class TestBugSeverityPriority(unittest.TestCase):
    def setUp(self):
        self.tracker = BugTracker()

    def test_bug_severity_and_priority_display(self):
        # Create a bug with severity 'Critical' and priority 'High'
        bug = Bug(title='App crash on login', severity='Critical', priority='High')
        self.tracker.add_bug(bug)

        # Retrieve the bug from tracker
        retrieved_bug = self.tracker.get_bug_by_title('App crash on login')

        # Assert severity is 'Critical'
        self.assertEqual(retrieved_bug.severity, 'Critical')

        # Assert priority is 'High'
        self.assertEqual(retrieved_bug.priority, 'High')

if __name__ == '__main__':
    unittest.main()

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test framework initialized, no bugs in tracker	—	PASS
2	Create a bug with severity 'Critical' and priority 'High'	Bug object created with given severity and priority	—	PASS
3	Add the bug to the bug tracker	Bug tracker contains one bug with title 'App crash on login'	—	PASS
4	Retrieve the bug by title from the tracker	Bug object retrieved with severity 'Critical' and priority 'High'	—	PASS
5	Assert the bug severity is 'Critical'	Bug severity is 'Critical'	Check if retrieved_bug.severity == 'Critical'	PASS
6	Assert the bug priority is 'High'	Bug priority is 'High'	Check if retrieved_bug.priority == 'High'	PASS
7	Test ends successfully	Bug severity and priority verified correctly	—	PASS

Failure Scenario

Failing Condition: Bug severity or priority is not set or retrieved correctly

Execution Trace Quiz - 3 Questions

What does the test verify about the bug?

A That the bug's description is displayed

B That the bug's severity and priority labels are correctly assigned and retrieved

C That the bug is automatically fixed

D That the bug is deleted after creation

Key Result

Always verify that bug tracking systems correctly handle both severity and priority fields, as they guide developers on impact and fix order.

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