Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Metrics for manual testing

10,181 views

Published on

  • Best dissertation help you can get, thank god a friend suggested me ⇒⇒⇒WRITE-MY-PAPER.net ⇐⇐⇐ otherwise I could have never completed my dissertation on time.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1url.pw/FQBG5 ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I'd advise you to use this service: HelpWriting.net The price of your order will depend on the deadline and type of paper (e.g. bachelor, undergraduate etc). The more time you have before the deadline - the less price of the order you will have. Thus, this service offers high-quality essays at the optimal price.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1url.pw/FQBG5 ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Defect discovery rate. If it is high, is that good or bad. If it is low, is that good or bad. Metrics are supposed to help make decisions. What does this metric tell you. Its only use is to make estimates for the next project run by the same team.
    Defect Severity - If the severity is high, what do you do? If the severity is low, what do you do? There is no known mechanism for selectively finding the sever problems. Thus, the fraction of all defects found that are sever will be the fraction of the delivered defects that are sever.
    Defects Rejected. You should record all problems, even is they are rejected. Otherwise you may miss something important.
    If you have a proposed metric, ask yourself what you will do if the value is high and what you will do if the value is low. If you have no answer or if the answer is the same in either case, don't use the metric. You will just waste time and piss off the developers.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Metrics for manual testing

  1. 1. Metrics – Manual Testing Anup Panigrahi 1
  2. 2. IntroductionMetrics collected during various phases of testing has been describedfor the different phases in the following slides.1) Requirement Phase2) Test Design Phase3) Test Execution Phase 2
  3. 3. Requirement Phase 3
  4. 4. Requirement PhaseFormula:(Total number of Original Requirements + Cumulative number of requirements changed (till date) + Cumulative number of requirements added (till date) + Cumulative number of requirements deleted (till date)) / (Total number of Original Requirements)Description:This metric is calculated taking added, deleted, changed requirements into consideration.This helps to identify the exact requirements that are required for further design activities. 4
  5. 5. Requirement Stability IndexFormula: (based on Effort)((Estimated Effort for the completed/ongoing stages) / (Estimated Effort for the completed/ongoing stages - Effort Estimated for Changes till that stage)))Description:This metric is used to calculate the Requirement stability index based on the effort spent on the requirement analysis 5
  6. 6. Requirements Leakage IndexFormula:(No. of missed Requirements / No. of Initial Requirements)Description:This metric helps to identify the requirements that have possibly been missed out during the requirement analysis phase. 6
  7. 7. Test Design Phase 7
  8. 8. Test Case Preparation ProductivityFormula:(No of Test Cases /scripts) / (Effort spent for Test Case/Script Preparation)Description:Test case preparation productivity is used to calculate the number of test cases prepared and the effort spent for the same. 8
  9. 9. Test Execution Phase 9
  10. 10. Test Case Pass PercentageFormula: (Total Number of test cases or scripts executed and passed / Total Number of test cases or scripts prepared)*100Description: The metric calculates the test case pass percentage which helps to determine the functional coverage of the business components 10
  11. 11. Test Case Execution PercentageFormula: (Total number of test cases or scripts executed/Total number of test cases or scripts prepared)*100Description: The metric calculates the test case execution percentage, from which the execution efficiency can be measured 11
  12. 12. Defect Summary• Description: Defect summary gives the status of the defects, whether it falls in the following categories: Submitted (New/Open), Re/Assigned, Fixed, Verified, Closed, Rejected, Duplicate, Deferred. 12
  13. 13. Defect Discovery RateFormula: Total number of defects found in application /Number of test cases or scripts executed.Description: This metric is useful to calculate the rate of identifying defects based on the test cases executed. This metric helps to evaluate the efficiency of the team in identifying the defects. 13
  14. 14. Defect SeverityDescription: Defect Severity helps to classify the defects based on the following categories: Critical, Serious, Important, Non Critical, Out Of Scope. Defects are given importance based on the severity. For example, Critical and Serious defects has to be given immediate attention , so that these defects does not affect the business functionalities. Module wise severity is also calculated which gives the defect severity for each module. i.e., System Crash is a Critical Defect (Severity 1) 14
  15. 15. Defect DensityDescription: This metric shows the defect population in each module. Based on this metric, attention is paid to the module which has more defects as well as high defect density percentage. This metric also helps to compare the defects spread across all modules and take necessary action accordingly. 15
  16. 16. Defect Rejection RatioFormula: (Defects Rejected/Defects Raised)*100Description: This metric is used to calculate the percentage of defects that has been rejected among the overall defects raised. Defects have to be verified and analyzed before logging to avoid high rejection ratio.Notes: We should not consider the defects those are rejected due to Business reasons, or sometime rejection happens as the Business seeing no scope to fix it, or Browser Issue, Cancelled, Out of Scope, Region Issue, etc. 16
  17. 17. Thank You! 17

×