goksn

 Profile Answers by goksn 

• Aug 13th, 2009

 

We can divide metrics in testing projects into two types

1. Metrics needed for test manager(some times-clients) for measuring the testing team's performance.

Here we can say

(i) Test Case Efficiency
(ii) Defect Unearthening ratio
(iii) Ratio of 'defects found by testers' Vs 'Defects found in production by non-testers'

etc

2. Metrics needed for development team/other senior management for getting the health of the product / project with respect to testing.

Here again we can divide into two major categories

2.1 Test case wise metrics
        (i) No.of test cases planned,executed,passed,failed,blocked etc across builds,modules, phases, dates etc.

2.2 Defect wise metrics
        (i) P1,P2,P3,S1,S2,S3 bugs against dates, builds, modules,phases etc.

I have not elaborated metrics in each and every category instead i just figured out the types.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Nov 18th, 2009

 

A Test metric is a standard means of measuring some attribute of the software testing process.  They establish test progress against the test schedule and may be an indicator of future results.  Metrics are produced in two forms – base and derived metrics.

Examples of base metrics:
# New test cases
# Regression test cases
# Test cases run
# Test cases not run
# Passes
# Fails
# Test cases under investigation
# Test cases blocked

Examples of derived metrics:
% Test cases complete
% Test cases passed
% Test cases failed
% Test cases blocked
% Test defects corrected

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 28th, 2009

 

Hi

Metrics can be prepared at any level of SDLC

Requirements:

-> Schedule Variance
-> Effort Variance
-> Frequency of CR's, etc

Testing:

-> Test cases count per module
-> Test cases types: Functional or non functional
-> Execution Report : How many executed, how many unable to execute..etc
-> Result Related metrics: How many are passed, how many failed,etc


CNU