Creating Test Templates

Test Case: [Brief descriptive name]

Description:
[What is being tested and why]

Steps:
1. [First action to take]
2. [Second action to take]
3. [Continue with specific steps]

Expected:
[What should happen if working correctly]

Actual:
[What actually happened - fill during execution]

Notes:
[Additional observations, issues, or context]

Progress:

• Define test objective and scope
• Write clear, descriptive test case name
• Document comprehensive description
• Break down into executable steps
• Define expected outcomes
• Leave actual results blank for execution
• Add notes section for observations

Example 1: Input: "Need to test login functionality" Output:

Test Case: User Login with Valid Credentials

Description:
Verify that users can successfully log into the system using valid username and password combinations.

Steps:
1. Navigate to login page
2. Enter valid username in username field
3. Enter valid password in password field
4. Click "Login" button

Expected:
- User is redirected to dashboard
- Welcome message displays user's name
- Navigation menu becomes available
- Session is established

Actual:
[To be filled during test execution]

Notes:
- Test with multiple user roles
- Verify session timeout behavior

Example 2: Input: "API endpoint testing" Output:

Test Case: GET /api/users Endpoint Response

Description:
Validate that the users API endpoint returns proper data structure and HTTP status codes.

Steps:
1. Send GET request to /api/users
2. Verify response status code
3. Check response headers
4. Validate JSON structure
5. Confirm data types match schema

Expected:
- Status code: 200
- Content-Type: application/json
- Response contains array of user objects
- Each user has id, name, email fields

Actual:
[To be filled during test execution]

Notes:
- Test with different authentication levels
- Verify pagination parameters