Managing Test Coverage


It's clear that even simple use cases can drive a significant number of test cases. For many applications, testing all use cases at this level of thoroughness, at least for each successive release, may not be feasible . In higher assurance systems, however, it is likely that every specific test case not only will be identified but also must be rerun on every subsequent software release. Without tooling, this becomes a significant effort; with proper tooling, the effort is more manageable. Here are a few simple guidelines to help you think through this part of the testing challenge.

  • Select the most appropriate or critical use cases for the most thorough testing. Often these use cases are primary user interfaces, are architecturally significant, or present a hazard or hardship of some kind to the user should a defect remain undiscovered.

  • Choose each use case to test based on a balance between the cost, risk, and necessity of verifying the use case.

  • Determine the relative importance of your use cases by using a priority algorithm specific to your context.


Managing Software Requirements[c] A Use Case Approach
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
Year: 2003
Pages: 257 © 2008-2017.
If you may any questions please contact us: