Test Case Documentation

When writing test cases, please keep in mind these points:

  1. Reusability

Write test cases that are reusable across different versions of the application. This will save time and effort in the long run, especially for **regression testing.**

  1. Maintainability

Ensure that test cases are easy to maintain as the website evolves. Update test cases when requirements change and ensure they remain relevant and accurate over time.

TC Template

Tips for TC title

<aside> 💡

Don’t begin with Verify/Check(it is obvious a test case main job is to check or verify). Make it clear and concise using: FEATURE → ACTION → EXPECTED RESULT method.

Examples:

TC - Navigation Menu – Click on a Menu Item – Redirects to the Correct Page

TC - Homepage Layout – View on Mobile – Content Adjusts Without Overlapping

Expected Result may vary for the Type of Testing is being done.

</aside>

[TEMPLATE FOR STEPS] - copy this format for the TC description 

**Step 1:**
//Write here step 1
- [ ] **Expected Results:**
//Write here expected Results

**Step 2:**
//Write here step 2
- [ ] **Expected Results:**
//Write here expected Results

**Step 3:**
//Write here step 3
- [ ] **Expected Results:**
//Write here expected Results

//Add as many steps as u need using the same format

Test Case Labels for Workflow

QAReview Added by a Tester who needs advice/help from a Lead or Senior
Blocked Test Case is blocked by another Test Case, execution will be postponed until the blocker Test Case is executed.
CNT Test Case is invalid/outdated and it can no longer be tested.
NMI Test Case needs More Information from the Author. (update or comment with further information)
Test Case Automatically added when using the Test Case Template.
Duplicate Test Case is a duplicate after another TC and will be closed.
Regression Only used for adding a Test Case to the Regression Test Suite

Test Case Workflow Cases 🔀📝

Test Case Writing📄