Answer» - Severity - Severity in testing refers to how MUCH of an impact it has on the computer program under test. A higher severity rating indicates that the bug/defect has a greater impact on system functionality. The severity level of a bug or defect is usually determined by a Quality Assurance engineer.
- Priority - The order in which a fault should be repaired is referred to as a priority. The higher the priority, the faster the problem should be fixed. Flaws that render the software system unworkable are prioritized over defects that affect only a tiny portion of the software's functionality.
The following table lists the differences between priority and severity - | Priority | Severity |
|---|
| The sequence in which a developer should fix a bug is determined by priority. | The severity of a defect is defined as the impact it has on the PRODUCT's operation. | Priority is divided into three categories : The bugs are usually assigned priority labels like P0, P1, P2 and so on, where P0 denotes the bug with the highest priority. | There are five types of severity : - Critical
- Major
- Moderate
- Minor
- Cosmetic
| | Priority is linked to the scheduling of bugs in order to resolve them. | Severity is linked to the functionality or standards of the APPLICATION. | | Priority denotes how urgently the fault should be corrected. | Severity denotes the severity of the defect's impact on the product's functionality. | | In consultation with the manager/client, the priority of defects is determined. | The defect's severity level is determined by the QA engineer. | | Its WORTH is subjective and might fluctuate over time based on the project's circumstances. | Its worth is objective and unlikely to fluctuate. | | When a problem has a high priority and low severity, it means it needs to be corrected right away but isn't affecting the application. | When a fault has a high severity and a low priority, it means it needs to be corrected, but not right now. | | The priority status is determined by the needs of the consumer. | The product's technical aspect DETERMINES the severity level. | | During UAT (User Acceptance Testing), the development team prioritizes defects and fixes them. | During SIT (System Integration Testing), the development team will prioritize and resolve bugs based on their severity. |
|
