Effective review of test cases

ERTC3

Objective

The objective of this masterclass is to enable the participants to assess the adequacy, execution efficiency and future automation-ability of test cases.

Target audience

Test leads and Test engineers


 


Content

Good defects are the result of effective test cases. Test effectiveness is a function of the quantity and quality of test scenarios/cases. The difficult aspect is in assessing if the designed scenarios/cases are indeed adequate. As always, a deep business domain and technical knowledge is seen as a critical aspect to effectively review the test scenarios/cases.

know more

The challenge is that deep domain/technical skills are always in short supply. This workshop outlines a scientific approach to assess the quality of test scenarios/cases by applying a goal centered view to testing – “What types of defects should I detect”?. Commencing with identification of potential defect types that may impact customer experience, the designed scenarios/cases are analyzed for fault coverage in addition to requirements coverage. To ensure that the test cases can be executed efficiently, the test cases are analyzed from the perspectives of conformance and robustness, business-risk/priority and then fitness for automation-ability.

Details

A well architectured set of test cases is like a effective bait that can ‘attract defects’ in the system. It is equally important to ensure that they are well organized to enable execution optimization and have the right set of information to ensure easy automation. Using the metaphor of a fish-net to testing, the masterclass will enable the assessment of Test breadth (how wide is the net), Test depth (how deep is the net) and Test porosity(how small are the holes in the net) to help judge test effectiveness.

Program content

  • Understanding the goal of TS/TC i.e. what types of defects should we detect?
  • Assessing basic completeness using RTM (Requirement traceability matrix)
  • Understanding the caveat of RTM i.e. it is necessary but not sufficient enough
  • Understanding fault traceability matrix
  • know more
  • Understanding the STEM-TCA and their objective
  • Level and type analysis
  • Adequacy analysis
  • Test focus analysis
  • Automation-ability analysis
  • Test documentation completeness
  • Limitations of black box techniques
  • What information related to internal aspects of the software do I need to know i.e. how to use white box techniques effectively
  • Measurements – Test breadth, Test depth and Test porosity