Skip to main content

Test case review checklist

Test case ID:

  • Test case is unique
  • Test case can be identified by its ID

Test case title/description:

  • The test case title describes the test purpose clearly and briefly
  • The test case description clearly defines the purpose of the test

Preconditions:

  • All necessary preconditions to execute the test are specified
  • All preconditions are relevant to the test case
  • The preconditions set up the test environment correctly
  • Repetitive test steps are documented as preconditions
  • Preconditions are designed to be reusable

Postconditions:

  • All critical aspects of the system’s state are validated
  • All postconditions are relevant to the test case
  • Postconditions are designed to be reusable

Test steps:

  • Test steps are clear and sequential
  • Test steps can be executed without ambiguity
  • Test steps are not chained together as one step
  • Test steps do not include expected results vThere shouldn’t be more than 15 steps in a single test case
  • Test steps do not include unnecessary data
  • Test steps are designed to be reusable

Expected results:

  • Expected results are defined precisely and concisely
  • Expected results are measurable
  • Expected results are relevant to the test
  • All expected results are documented
  • Expected results are designed to be reusable

Error handling and edge cases:

  • The tests include negative scenarios
  • Expected error messages or failures are documented

Environment:

  • Test environment is clearly defined (specific hardware, OS, browser, etc)
  • Dependencies and necessary configurations are documented

Test data:

  • The test data is relevant and appropriate to the test case
  • The test data is accurate and formatted correctly
  • The test data is complete

Grammar and quality:

  • The test case is formatted consistently with other test cases
  • The language used for the test case demonstrates professionalism
  • The test case is written without errors (typos, grammatical errors)
  • The test case is not a duplicate of an existing test case
  • The test case covers one feature
  • The test case is written from an end-user perspective
  • The test case maps directly to a specific requirement
  • The test case has an appropriate priority