Test Cases

Test cases are the blueprint of manual tests, written in GIVEN-WHEN-THEN Gherkin syntax.

For detailed guidelines on writing test cases, see: Manual Testing Guidelines

Test Case Template

Use the template below to create a new test case:

##

- Description:
- Given
- When I
- Then I
- Execution Time:
- E2E Implementation Complexity:
- E2E Implementation Status:
- Regression Likelihood:
- Level of Criticality:
- Actual Result:
- Test Result:
- Notes:

Important:

Note: Don't estimate individual tests, but a whole group of tests. - E2E Implementation Complexity: Estimated effort to automate the test - E2E Implementation Status: Status of automation (e.g., Not started, In progress, Implemented) - Regression Likelihood: <Low|Medium|High|Critical> based on historical data and code stability - Level of Criticality: <Low|Medium|High|Critical> based on user impact and business value

Automation Candidate & Effort Analysis Guidance:

  • Consider execution time of manual tests – longer manual tests are good candidates for automation.
  • Balance test value vs. automation effort.
  • Don't estimate individual tests, but a whole group of tests.
  • For each manual test, estimate automation effort analysis:
    • E2E Implementation Complexity: Estimated effort to automate the test
    • E2E Implementation Status: Status of automation (e.g., Not started, In progress, Implemented)
    • Regression Likelihood: <Low|Medium|High|Critical> based on historical data and code stability
    • Level of Criticality: <Low|Medium|High|Critical> based on user impact and project value