Priority and Severity- Mobile App Testing

A bug is an error, defect or a flaw related to the software system which would result in incorrect or unexpected behavior. Mobile apps are also needed to be tested and bugs need to be resolved before published to the App Store. But these bugs are needed to be classified according to the impact to the business or functionality.

The defects are basically classified using two important constraints.

  • Priority
  • Severity


Priority is the important constraint which defines the order in which the defect needs to be fixed.  Priority can be Low, Medium or High. If the priority is high, the defect needs to be fixed earlier than other priority defects.

Defect priority is classified into three class:

Low: The issue is pinpicky but can be done once the more serious defect has been fixed
Medium: The issues that need to be resolved once the high is resolved. It can wait until a new version as well.
High: The issue that needs to be resolved as soon as possible as it affects the system severely and cannot be used until it is fixed.

Priority is associated with the scheduling and is provided by the consultation with the Manager & Client.


Severity is another important constraint which defines the impact/effect of the issue on the software system under test.  Severity is usually can be Blocker, Critical, Major or Minor. If the defect is Blocker or Critical, the defect is affecting the usage or operation of the software system.

Severity is usually associated with the functionality and is provided by the Quality Assurance Engineer.

Defect Severity can be classified into four class:

Blocker: The issue blocks the usage of the application and the software system is unusable.
Critical: The issue indicates complete shut-down of the feature.
Major: The issue is high severity defect where important functionality is not working as expected. However, the other parts of the system remain functional
Minor: The issue is minor but the software system is still functional.

Below are some of the examples of the combination of Priority and Severity in case of mobile app testing.

  • High Priority – Critical Severity: Key Features such as Login or Search functionality not working as expected.
  • High Priority –  Non-Critical Severity : Company Logo is not correct in the app or Invoice generated.
  • Low Priority – Critical Severity: Feature which are rarely used such as Video Ad Playback etc are not working.
  • Low Priority – Non-Critical Severity: Minor UI issues and Image rendering issue in the app.

It is always important to classify the defect based on these two important constraints. Classification of defect appropriately would lead to early fixing of the critical defect and helps with the stable development of the apps.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Powered by

Up ↑

%d bloggers like this: