Test Case Creation

Types of BA Test Cases

1. Happy Path (Positive)

The standard flow working perfectly.

• "User enters valid email/pass -> Logs in successfully."

2. Negative Path (Error Handling)

Trying to break it / Invalid inputs.

• "User enters invalid email -> Shows error message 'Invalid format'."

3. Edge Cases (Boundary)

Testing limits.

• "User enters exactly 255 characters (max) -> Accepted."
• "User enters 256 characters -> Rejected."

4. Business Logic / Complex Flow

Multi-step scenarios.

• "User adds item -> Apply Discount -> Remove Item -> Verify Total recalculates."

Test Case Template

Scenario: Apply Promo Code

Traceability

Ensure every Test Case links back to a Requirement (FR).

• TC-PROMO-01 <--> FR-CART-05 (Promo Codes).

Best Practices

• One Verification per Test: Don't test 10 things in one case. If one fails, the whole case fails.
• Be Specific: Don't say "Check result". Say "Verify text says 'Success'".
• Clean Up: Tests should clean up data (Postconditions) so the next test isn't blocked.

Tools

• Lark Base / Excel: Simple test tracking.
• Jira / Zephyr / Xray: Integrated test management.
• TestRail: Dedicated test tool.