🇺🇸English

Test Case Creation Skill

Purpose

Translate requirements into executable steps to verify the system works as expected. While QA executes tests, BAs often define the scenarios to ensure business logic is covered.

When to Use

• During Requirements phase (to ensure testability).
• UAT Planning (writing scripts for users).
• Reviewing QA Test Plans (validation).

Anatomy of a Good Test Case

1. ID : Unique (e.g., TC-001).
2. Title : Concise summary.
3. Preconditions : Setup required (e.g., "User logged in").
4. Test Steps : Step-by-step actions using imperative verbs ("Click", "Enter", "Verify").
5. Test Data : Specific data used (e.g., "Email: test@example.com").
6. Expected Result : What should happen? (Specific).
7. Postconditions : State after test (e.g., "Order created in DB").

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.