What is the difference between priority and severity?
Theme: Defect Management Role: Qa Engineer/Test Engineer Function: Technology
Interview Question for QA Engineer/Test Engineer: See sample answers, motivations & red flags for this common interview question. About QA Engineer/Test Engineer: Ensure software quality through testing and quality assurance. This role falls within the Technology function of a firm. See other interview questions & further information for this role here
Sample Answer
Example response for question delving into Defect Management with the key points that need to be covered in an effective response. Customize this to your own experience with concrete examples and evidence
- Definition: Priority refers to the order in which defects or issues should be addressed based on their importance or urgency. Severity refers to the impact or seriousness of a defect or issue on the system or its functionality
- Measurement: Priority is typically measured on a scale of high, medium, or low, indicating the urgency of fixing the defect. Severity is measured on a scale of critical, major, minor, or cosmetic, indicating the impact on the system
- Focus: Priority focuses on the order of fixing defects, considering business needs and deadlines. Severity focuses on the impact of defects on the system's functionality and user experience
- Decision-making: Priority is determined by project managers or stakeholders based on business requirements and project goals. Severity is determined by testers or QA engineers based on the impact of defects on the system
- Relationship: Priority and severity are related but not always the same. A defect with high severity may not always have high priority if it does not impact critical functionality or business goals. Similarly, a defect with low severity may have high priority if it affects critical functionality
- Example: For example, a defect that causes the system to crash when performing a crucial operation would have high severity as it affects the system's functionality. However, if the operation is rarely used, it may have low priority as it does not impact critical business goals
Underlying Motivations
What the Interviewer is trying to find out about you and your experiences through this question
- Knowledge & understanding of QA concepts: Assessing if the candidate has a clear understanding of priority and severity in the context of software testing
- Analytical skills: Evaluating the candidate's ability to differentiate and analyze the impact and urgency of defects
- Attention to detail: Determining if the candidate pays attention to the severity of defects and prioritizes them accordingly
- Communication skills: Assessing if the candidate can effectively communicate the difference between priority and severity to stakeholders
Potential Minefields
How to avoid some common minefields when answering this question in order to not raise any red flags
- Confusing priority & severity: Mixing up the definitions or using them interchangeably
- Lack of understanding: Not being able to explain the difference clearly or providing incorrect examples
- Limited knowledge: Not being aware of the importance of priority and severity in software testing
- Inability to prioritize: Not being able to explain how to prioritize defects based on severity and impact