TEST METRICS

Test Metrics
---------------
‘Metric’ is a measure to quantify software, software development resources, and/or the software development process.
A Metric can quantify any of the following factors:
Schedule Variance
Work Effort
Product Size
Project Status
and Quality Performance

Few of Defect metrics
Defect Density:-
Defect Density=No of defects reports by QA+No of defects report by Peer or client /Actual size of the project
The Size can be in KLOC, SLOC, or Function Points. The method used in the Organization to measure the size of the Software Product.

KLOC = Thousand lines of code 1 K= 1000 lines SLOC = Source lines of code 1000 SLOC = 1KLOC this is used to compare the relative number of defects in various software components, to find out the defect prone areas of the application.

Test Effectiveness :-
Test Effectiveness=T/T+UAT
T= Total no of defects reported during testing
UAT=Total no of defects reported during user acceptance testing.

Overall Test Effectiveness (OTE)
This metric will indicate the effectiveness of the Testing process in identifying the defects for a given project during the testing stage

Overall Test Effectiveness: OTE = [(Number of defects found during testing) / (Total number of defects found during Testing + Number of defects found during post delivery)] * 100

Defect Removal Efficiency:-
DRE=(Total No Of Defects Removed or Resolved /Total No. Of Defects Injected)*100 at various stages of SDLC

Defect Leakage:-
Defect leakage is nothing but defect identified by the client

Defect Age:-
Duration between defect found and closed.

Schedule Variance (SV)
This metric gives the variation of actual schedule vs. the planned schedule. This is calculated for each project – stage wise
Percentage of time taken to complete the task
SV = [(Actual no. of days – Planned no. of days) / Planned no. of days] * 100

Effort Variance:-
This metric gives the variation of actual effort vs. the estimated effort. This is calculated for each project Stage wise.
EV = [(Actual person hours – Estimated person hours) / Estimated person hours] * 100

Cost Variance (CV)
This metric gives the variation of actual cost Vs the estimated cost. This is calculated for each project Stage wise
CV = [(Actual Cost – Estimated Cost) / Estimated Cost] * 100

Size Variance
This metric gives the variation of actual size Vs. the estimated size. This is calculated for each project stage wise
Size Variance = [(Actual Size – Estimated Size) / Estimated Size] * 100

Review Effectiveness
This metric will indicate the effectiveness of the Review process
Review Effectiveness = [(Number of defects found by Reviews) / ((Total number of defects found by reviews) + Testing)] * 100

How do you determine metrics for your application?

Objectives of Metrics are not only to measure but also understand the progress to the Organizational Goal.
The Parameters for determining the Metrics for an application:
Duration Complexity
Technology Constraints
Previous Experience in Same Technology
Business Domain Clarity of the scope of the project

Goal Question Metric methods for identifying metrics :-

Goal question metric methods for identifying metrics is an excellent technique for selecting appropriate metrics to meet your needs. The GQM works like this :Begin by selecting few projects or organization goals. State the goals in quantitative and measurable term as possible. Then find out what must be change to reach the goal, and identify ,define what is to measured to quantify progress made to achieve the goal.

• GQM is a systematic approach for integrating goals to the process
• The metrics relevant to process improvement can be effectively identified and tailored to the organization and its goals.
• Measurement provides the most appropriate information to ensure consistency and completeness in the quest for goal attainment

When do you determine Metrics?
When the requirements are understood in a high-level, at this stage, the team size, project size must be known to an extent, in which the project is at a "defined" stage