Test case document

Objective of documenting the test cases is to re-use in future and to ensure that the test cases are complete enough to detect all possible types of issues that may occur.  For the rapid and effective assessment of test case completeness and effectiveness, form and structure of the test case matters a lot. Here form and structure refers to the categorization of test cases. HyBIST has a NINE level categorization of test cases for the deeper analysis. The basic FOUR attributes that every test case has to be tagged are,

  1. Test case has to be tagged by Item (EUT) – to know the completeness
  2. Test case has to be tagged by Level – to know what type issues targeted
  3. Test case has to be tagged by type – to know whether we have considered both conformance and robustness
  4. Test has to be tagged by priority – to know the importance of test case for a rapid selection for regression
Leave a Reply 0

Your email address will not be published. Required fields are marked *