Why to Track Software Bugs Density?

Why to Track Software Bugs Density?
October 31 10:00 2013 Print This Article

One of the criteria used for predicting completion and planning testing activities is software bugs density. It shows how many errors are discovered per certain requirement or functionality during mobile testing, desktop testing or web site testing.

Any tester’s aim is to find as many software bugs as possible in tested application. Some areas of a software product contain many defects, some few. If there are a lot of defects in a certain application area a software testing company must find out the reason.

Often Reasons of High Density of Software Bugs Are:

  1. Unsuitable elaboration or /and coding of the function.
  2. Sophisticated and complex functionality which is hard to code.
  3. Incorrect understanding of the function and due to it utilization of improper resources for their implementation.

When estimating software bugs density one should also pay attention to their priority. A software product function may contain 20 low-priority errors and pass acceptance testing. Another software product function may have only 2 high-priority errors and do not meet the acceptance requirements because of them.

So, when executing software testing, one should pay attention to software bugs density as well as to priority of software bugs.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles


write a comment

No Comments Yet!

You can be the one to start a conversation.

Add a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person.
All fields are required.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.