Software Testing | Identifying bugs in different ways

Author - Webner

In software testing, we have various way to identify the bug/defect. Some of them are as given below:

1. Severity Wise:

* Major: When defect affects major functionality. Example: Suppose a Logo text is not Proper that will be affect the company work.
* Minor: When defect affects minor functionality or non-critical data. Example: Spelling mistakes in text of home screen.
* Fatal: When defect will cause the system to crash or close abruptly. Example: Runtime Errors like JavaScript errors etc.

2. Work product wise:

* SRS: A defect from System Requirement Specification.
* FRS: A defect from Functional Requirement Specification.
* BRS: A defect from Business Requirement Specification.
* DDS: A defect from Detailed Design document.
* Source code: A defect from Source code.
* Test Plan/ Test Cases: A defect from Test Plan/ Test Cases.

3. Type of Errors Wise:

* Comments: When comment is missing in source code.
* Computational Error: When validation is not correct in code.
* Data error: When update from database is not correct.
* Database Error: When error is showing in database design.
* In correct Design: When design is incorrect.
* Boundary Value Conditions Neglected: When boundary Value conditions incorrect.
* Interface Error:
When alignment is incorrect.
When unfriendly behaviour of application.
When passing of parameter handling is incorrect.
* Logic Error: When irrelevant functionality in source code.
* Message Error: When missing error message is showing in source code.
* Navigation Error: When navigation code is not correct in source code.
* Performance Error: When performance is not good of the application.
* Inadequate Requirements: Requirement needs additional inputs for to be complete
* Incorrect Requirements: When requirement is incorrect.
* Ambiguous Requirements: When requirement is not clear. Includes ambiguous word – example: Like, such as, may be, could be, might etc.
* Standards: When standard is improper of exception handling.
* System Error: When hardware and operating System related error.
* Test Plan / Cases Error: When incorrect test Plan/case.
* Typographical Error: When spelling mistake in source code.
* Variable Declaration Error: When improper declaration of variables.

4. Status Wise:

* Open
* Closed
* Deferred
* Cancelled

5. Priority Wise:

* High: When immediate fix of the defect is needed.

For Example:  Spelling mistake on menu item name which is getting highlighted to the end user.

* Medium: When no need of immediate fix of the defect.

For Example: When application shows some undesirable behavior in a particular case.

* Low: Fixing can be deferred until all other priority defects are fixed. It may or may not be fixed at all.

For Example: When the application crashes after multiple use of any functionality like – Click of Save button 200 times crashes the application.

Webner Solutions is a Software Development company focused on developing Insurance Agency Management Systems, Learning Management Systems and Salesforce apps. Contact us at for your Insurance, eLearning and Salesforce applications.

Leave a Reply

Your email address will not be published. Required fields are marked *