Build NQuality Score To Measure The Build Health

Managers always end up asking the health of the build to the test engineers but most of the time it happens that engineer cant give any absolute answer for this question. Many organizations create large number of graphs to convey the health of the build but it happens that no one will be patient enough to go through all the graphs so I felt the necessity of having just one value which gives clear picture of the build health.
Build NQuality Score (BNQS) is parameter which gives the value which indicates the health of the build. Zero BNQS would mean a very high quality build and large values indicate the poor quality. Ideally BNQS not just indicates the build health but also how close are we to release/ sign-off.

How to Calculate BNQS:
Consider the following parameters:
  1. Open/Resolved bugs for the build at the start of build testing O={o1,o2,o3…} with each bug of different severity {critical, high, medium, low}.
  2. Requests logged for the build X L={l1,l2,l3…} with each bug of different severity {critical, high, medium, low}.
  3. Requests verified for the build X V={v1,v2,v3…} with each bug of different severity {critical, high, medium, low}. (These should include only requests which are verified and not reopened)
Associate weight with each of severities {critical, high, medium, low} as {w1,w2,w3,w4} where w1=1.0, w2=0.75, w3=0.50, w4=0.25. (These values can be different based on how exactly the organization is setting the severity of the request). Now the BNQS is calculated as :
BNQS= (Weighted sum of all open requests)+(Weighted sum of all logged requests)-(Weighted sum of all verified requests)
Where the weights mentioned in weighted sum are those associated with criticality.

An Example:
Initailly say there are 2 bugs (1 critical and 1 medium)
In Build 1, say 2 bugs are logged (both critical) and 1 is verified(medium) then
BNQS = (1*1+1*0.75)+(2*1)-(1*0.75) = 3 (for Build1)
In Build 2, say 1 bugs is logged (medium) and 1 is verified(critical) then
BNQS = (3*1) +(1*0.75)-(1*1) = 2.75(for Build2)
In Build 3, say 0 bugs are logged and 3 are verified(2 critical, 1 medium) then
BNQS = (2*1+1*0.75) +(0)-(2*1+1*0.75) = 0(for Build3)

Build Health Graph:
This is ideal case wherein the BNQS was zero for last build, but many times some of bugs gets deferred to future versions in which case BNQS will not be exactly zero. Ideally the graph should keep going down with each build.

Please feel free to comment on what you think about this article.


  1. Anonymous7:25 PM

    You are quite true. These sort of parameters will make everybody to understand the actual status of the project. we can say that it will bring transipiracy :)

    - Manu

  2. Anonymous1:06 PM

    i have seen your web page its interesting and informative.
    I really like the content you provide in the web page.
    But you can do more with your web page spice up your page, don't stop providing the simple page you can provide more features like forums, polls, CMS,contact forms and many more features.
    Convert your blog "" to completely free.
    free Blog services provide only simple blogs but we can provide free website for you where you can provide multiple services or features rather than only simple blog.
    Become proud owner of the own site and have your presence in the cyber space.
    we provide you free website+ free web hosting + list of your choice of scripts like(blog scripts,CMS scripts, forums scripts and may scripts) all the above services are absolutely free.
    The list of services we provide are

    1. Complete free services no hidden cost
    2. Free websites like
    3. Multiple free websites also provided
    4. Free webspace of1000 Mb / 1 Gb
    5. Unlimited email ids for your website like (,
    6. PHP 4.x
    7. MYSQL (Unlimited databases)
    8. Unlimited Bandwidth
    9. Hundreds of Free scripts to install in your website (like Blog scripts, Forum scripts and many CMS scripts)
    10. We install extra scripts on request
    11. Hundreds of free templates to select
    12. Technical support by email

    Please visit our website for more details and

    Please contact us for more information.


    HyperWebEnable team