Saturday, February 2, 2008

Measuring Software Testing

Usually, quality is constrained to such topics as correctness, completeness, security, but can also include more technical requirements as described under the ISO standard ISO 9126, such as capability, reliabilityefficiencyportabilitymaintainability, compatibility, and usability. And especially for Banking System, quality is constrained to Banking Regulation for each country.


Software Testing Measurements

There are a number of common software measures, often called "metrics", which are used to measure the state of the software or the adequacy of the testing:

  • Bugs found per Tester per unit time (Day/Week/Month)
  • Total bugs found in a release
  • Total bugs found in a module / feature
  • Bugs found / fixed per build
  • Number of customer reported Bug - As a measure of testing effectiveness
  • Bug trend over the period in a release (Bugs should converge towards zero as the project gets closer to release) (It is possible that there are more cosmetic bugs found closer to release - in which case the number of critical bugs found is used instead of total number of bugs found)
  • Number of test cases executed per person per unit time
  •  % of test cases executed so far, total Pass, total fail
  • Test Coverage

0 komentar: