Skip to content

Filling out a test page

Jump to bottom
PrestonCazier edited this page Aug 14, 2018 · 1 revision

Writing Good Test Cases

  • As far as possible, write test cases in such a way that you test only one thing at a time. Do not overlap or complicate test cases. Attempt to make your test cases ‘atomic’.
  • Ensure that all positive scenarios AND negative scenarios are covered.
  • Language:
    • Write in simple and easy-to-understand language.
    • Use active voice instead of passive voice: Do this, do that.
    • Use exact and consistent names (of forms, fields, etc).
  • Characteristics of a good test case:
    • Accurate: Exacts the purpose.
    • Economical: No unnecessary steps or words.
    • Traceable: Capable of being traced to requirements.
    • Repeatable: Can be used to perform the test over and over.
    • Reusable: Can be reused if necessary.

Test Suite: The ID of the test suite to which this test case belongs. The format is to use the initialism of the repo name(represented in this case by ***), followed by TSxxx, where xxx is the test suite number. A test suite is a grouping of test that can relatively be done together or in a sequence.

Test Case: The ID of the test case. use format TCxxx.

Summary: The summary / objective of the test case.

Related Requirements: The ID of the requirement this test case relates/traces to.

Associated Issue:

Prerequisites: Any prerequisites or preconditions that must be fulfilled prior to executing the test.

Test Procedure: list style step-by-step procedure to execute the test.

Test Data: The test data, or links to the test data, that are to be used while conducting the test.

Expected Result: hypothesis or the expected result of the test.

Actual Result: The actual result of the test; to be filled after executing the test.

Status: one of TO DO, IN PROGRESS, PASS, FAIL, or BLOCKED.

Remarks: written remarks regarding the important points that came up during the test case, or anything else of note.

Created By: @ person's name, this way we can link to the person that created the test case.

Date of Creation: written in MM/DD/YYYY.

Executed By: @ person's name, this way we can link to the person that excuted the test case.

Date of Execution: written in MM/DD/YYYY.

Test Environment: bullet point list of the variables that make up the test environment.

Clone this wiki locally