TestingDocs.com
Software Testing website
  • Automation
    • Selenium
    • JBehave Framework
  • Tutorials
    • MySQL Tutorials
    • Testlink
    • Maven
    • Git
  • IDEs
    • IntelliJ IDEA
    • Eclipse
  • Flowcharts
    • Flowgorithm
    • Raptor
  • About

Software Testing

Software Testing Metrics Overview

Overview

Metrics are the means by which the software quality can be measured, managed , improved etc. They provide the visibility you need into the product or process you follow. You may use different metrics for different purposes. Some examples of Testing metrics are the number of defects found, the number of test cases written etc.

Testing Metrics

There are lots of metrics that we can use to track progress of the project and measure the quality. Every project should be measured for its schedule, cost, effort and the quality. We will look at some of the testing metrics below. Each metric has different purpose.

Defect Density

The number of defects per KLOC or 1,000 lines of code. It is the ratio of the number of defects found vs. the total number of lines of code. This metric indicates the quality of the application under test.

Defect Density =  \LARGE \frac{ Number of Defects found }{Number of LOC(KLOC)}

 

For example, if a module has 2000 LOC. If 4 defects are uncovered during testing of the module. The defect density is :

Defect density of module =     \LARGE \frac{4}{2}

= 2

 

Note that = 2000 LOC = 2 KLOC.

Defect Removal Efficiency

This metric indicates the efficiency of defect removal methods used in the organization.It is the ratio of the number of defects that are removed per time unit. ( man hours or weeks ) . The total effort required for defect detection, resolution time and retesting time of the defects removed.

Defect Removal Efficiency = \LARGE \frac{ Number of Defects Removed }{ Effort Required forRemoval( hours/weeks)}

 

Testing Metrics

Test Coverage

It is calculated as the number of test cases executed or covered vs. the total number of test cases. This metric is an indication of the completeness of the testing. It provides a clue to which extent the testing covers the product’s requirements. Note that it does not indicate the effectiveness of the testing. Furthermore, this metric can be used as a criterion to stop testing.

Most of the time its is calculated as Percentage.

 

Test Coverage percentage = \LARGE \frac{NumberofTestCasesCovered}{TotalNumberofTestCases} * 100

 

For example, if the project has 100 total number of testcases and 25 cases have been executed then the

Test Coverage =  \LARGE \frac{25}{100} * 100

 

= 25% coverage.

Related Posts

PuTTY Tool UI

Software Testing /

Useful Tools for Software Testers

Errors Code Testing Development

Software Testing /

Error Density Metrics

Errors Code Testing Development

Software Testing /

Error Removal Effectiveness Metrics

RACI Chart

Software Testing /

RACI Chart

Android Calculator Icon

Software Testing /

Android Calculator Test Cases

‹ Static Testing vs Dynamic Testing› Statement Coverage

Recent Posts

  • Install RAPTOR Avalonia on CentOS
  • Download RAPTOR Avalonia Edition on Windows
  • npm doctor command
  • Print Triangle Pattern Flowchart
  • RAPTOR Editions
  • Flowgorithm Conditional Breakpoint Statement
  • Flowgorithm Read Numbers from File Example
  • Search Text File Flowchart Example
  • Flowgorithm Turtle Graphics Symbols
  • Draw Circle using Flowgorithm Turtle

Back to Top

Links

  • Contact
  • Privacy Policy
  • Cookie Policy

www.TestingDocs.com

Go to mobile version