Bug severity vs priority in Testing Fundamentals - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Bug Severity vs Priority

Which statement correctly describes the difference between bug severity and bug priority?

A Priority measures the impact on the system, while severity indicates how soon the bug should be fixed.

B Severity measures the impact on the system, while priority indicates how soon the bug should be fixed.

C Severity and priority both mean the same and can be used interchangeably.

D Priority is decided by developers, severity is decided by customers only.

💡 Hint

Think about what affects the system's functioning versus what affects the schedule.

Severity relates to how serious the bug's effect is on the system's operation. Priority is about how quickly the bug should be addressed based on business needs.

🧠 Conceptual

intermediate

Assigning Priority and Severity

A bug causes a minor UI misalignment but occurs on the homepage of a popular e-commerce site. How should severity and priority be assigned?

A High severity, high priority

B High severity, low priority

C Low severity, high priority

D Low severity, low priority

💡 Hint

Consider the bug's impact on system function and business urgency.

The bug has low severity because it does not break functionality, but high priority because it affects a key page and user experience.

❓ assertion

advanced

Bug Priority Assignment Logic

Given the following bug report, which priority level should be assigned?

Bug: Payment processing fails for all users.

Severity: Critical

A High priority because it blocks core functionality

B Medium priority because workaround exists

C No priority needed as severity is enough

D Low priority because it affects only payment module

💡 Hint

Think about how this bug affects business operations.

Payment failure is critical and blocks core business, so it must be fixed with high priority.

🧠 Conceptual

advanced

Impact of Priority and Severity on Release Planning

Which statement best explains how bug severity and priority influence release planning?

A Only bugs with high severity are fixed before release, regardless of priority.

B Bugs with low priority and high severity are always postponed to next release.

C Severity and priority do not affect release planning decisions.

D Bugs with high priority are fixed first, even if severity is low, to meet business goals.

💡 Hint

Consider business needs and deadlines in planning.

Priority drives the order of fixing bugs to align with business goals, even if severity is low.

🔧 Debug

expert

Analyzing Bug Triage Decisions

During bug triage, a tester marked a bug as 'High Severity' and 'Low Priority'. The developer fixed it last, but it caused a major customer complaint. What was the likely mistake in triage?

A The bug's priority was underestimated despite its high severity and customer impact.

B Severity was set too high; the bug was minor and should be low severity.

C Priority and severity should always be the same value.

D The developer ignored the triage and fixed bugs randomly.

💡 Hint

Think about how priority affects fixing order and customer impact.

High severity means serious impact, but low priority delayed the fix. Priority should reflect urgency to avoid customer issues.

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