Testing Fundamentals - Test Documentation
Which of the following is the correct way to classify a bug with 'Blocker' severity and 'Low' priority?
Which of the following is the correct way to classify a bug with 'Blocker' severity and 'Low' priority?
easy📝 Syntax Q3 of 15
Step-by-Step Solution
Solution:
Step 1: Understand 'Blocker' severity
Blocker means the bug stops system functions or blocks progress.Step 2: Understand 'Low' priority
Low priority means the fix is not urgent and can be delayed.Final Answer:
Bug stops all system functions but fix can wait -> Option CQuick Check:
Blocker severity + Low priority = Critical impact, delayed fix [OK]
Quick Trick: Blocker = stops system; priority decides fix speed [OK]
Common Mistakes:
- Assuming blocker bugs always have high priority
- Confusing severity with priority urgency
- Ignoring impact when priority is low
Master "Test Documentation" in Testing Fundamentals
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Testing Fundamentals Quizzes