Tuesday, 16 April 2013

What is a test cases review?

Software Testing plays a vital role in ensuring the quality of a Software product. Test cases are the key tools for testing. Test cases review has to be thorough in order to ensure that effective and adequate testing is done

What is the importance of test cases review?
  • Test cases are written with the intent to detect the defects
  • Understanding of the requirement is correct
  • Impact areas are identified and brought under test
  • Test data is correct and represent every possible class of the domain
  • Positive and negative scenarios are covered
  • Expected behavior is documented correctly
  • Test coverage is adequate
What is the methodology of test cases review?

Typically, reviews should be done during each phase in the Testing Life cycle
The phases involved in Software testing lifecycle are

Requirements understanding --During the Requirements Understanding phase, review of requirements is an activity that should be undertaken with utmost care and such review should be done systematically to ensure the clarity, correctness and testability of the requirements.
Test preparation--During the Test preparation phase, after the test scenarios are identified and test conditions and cases are built for each scenario, it is advisable to do a thorough and detailed review. Checklist for Test cases review during the Test Preparation Phase
Test Execution--During the test execution phase, doing a review after the cases are executed is very important .
Test Reporting--During the Test Reporting phase, it would help to ensure that all the required documents are prepared, metrics are collated and all the project specific formalities are completed.

What are the most common test case review defects?
  • Incomplete Test Cases
  • Missing negative test cases
  • No Test Data
  • Inappropriate/Incorrect Test data
  • Incorrect Expected behavior
  • Grammatical errors
  • Typos
  • Inconsistent tense/voice
  • Incomplete results/number of test runs
  • Defect details not updated
  • Changes to requirements not updated in Test case