CIGINITI:

Select instr(‘CORPORATEFLOOR’,3,2) out put

What are the reasons when data not loaded in target?

Severity vs Priority
Below are the differences between severity and priority:
Features Severity Priority

Severity is a parameter to denote Priority is a parameter to decide

Definition the impact of a particular defect on the order in which defects should
the software. be fixed.

Severity means how severe the

Priority means how fast the
Purpose defect is affecting the
defect has to be fixed.
functionality.

Severity is related to the quality Priority is related to scheduling

Relation
standard. to resolve the problem.

Categories Severity is divided into 4 Priority is divided into 3

 Features Severity Priority

categories:
categories:
 Critical
 Low
 Major
 Medium
 Medium
 High
 Low

Who decides The testing engineer decides the The product manager decides the
defects? severity level of the defect. priorities of defects.

Value Its value is objective. Its value is subjective.

Its value doesn’t change from time Its value changes from time to
Value change
to time. time.

It is associated with functionality

Association It is associated with scheduling.
or standards.

It indicates the seriousness of the It indicates how soon the bug

Indication
bug in the product functionality. should be fixed.

Driving factor It is driven by functionality It is driven by business value.

It is based on the technical aspect It is based on the customer’s

Based On
of the product. requirements.

Examples of Priority and Severity Combination

There are possible combinations of priority and severity:
1. High Severity High Priority: Consider an example of a web application where the
if after filling in the login details, the user cannot click the login button then this is the
case of high severity and high priority.
 High Severity: If the login button is not clickable then the whole application is
blocked and none of the functions can be accessed by the user
 High Priority: If the login button is not clickable this means that the application is
not letting any user log in then what is the use of such an application? Such defects
are high-priority defects as the users will avoid such applications and businesses
will be impacted.
2. High Severity Low Priority: Consider the example of the application being used
on the older versions of Internet Explorer say IE8. This is a case of high severity and
low priority.
 High Severity: The fault, in this case, is of high severity because when the
application is accessed on the older version, the page will not load properly and a
few fields and text will be overlapped thus whole application will be impacted.
 Low Priority: The defect is of low priority because very few actual users use IE8
or older versions so the fix can wait.
3. Low Severity Low Priority: Consider the example of the help or faq section of the
website where the theme or font style of a section of the page does not match with that
of the rest of the page.
 Low Severity: The defect is of low severity as the defect is not affecting the
website functionality.
 Low Priority: The defect is of low priority as not many users will access this
particular section of the website so the fix can wait.
4. Low Severity High Priority: Consider the example when there is a typo on the
website. For example, the case of the school website where the ‘Admission Form’ is
misspelled as ‘Admission Form’.
 Low Severity: The defect is of low severity because functionality-wise there is no
issue.
 High Priority: The defect is of high priority since it is related to business and
needs to be fixed as soon as possible.
Defect Triage
Defect triage is the process where each defect is prioritized based on its severity,
frequency, risk, etc. The goal is to evaluate, prioritize, and assign the resolution of
defects. This is mainly used in agile project management. The defect triage meetings
frequency depends on a number of factors:
 Project schedule.
 Overall project health.
 The number of bugs in the system.
 Impact on schedules of team members’ availability.
The defect triage process can be summarized as:
1. Defect Review: This step involves reviewing all the defects including the defects
that were rejected by the team.
2. Defect Assessment: This step involves an initial assessment of the defects based
on the content and respective priority and severity settings.
3. Defect Assignment: This involves prioritizing the defects, and assigning the
defects to the correct release by the product manager.