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.