Browse QA Engineers Section 6: API & Integration Testing

API Test Cases from Mobile Feature

5 fill-in slots · from The AI Prompt Handbook for QA Engineers

Your details

0/5 filled

API Test Cases from Mobile Feature

Generate API test cases for the backend calls made by this mobile feature.

FEATURE: [Description]
API ENDPOINTS USED:
1. [Method] [URL][Purpose]
2. [Method] [URL][Purpose]
3. [Method] [URL][Purpose]

AUTHENTICATION: [Bearer token / API key / OAuth]

For each endpoint, generate test cases for:

HAPPY PATH:
- Valid request with all required fields
- Valid request with optional fields included
- Valid request with minimum required fields only

VALIDATION:
- Missing required fields (one at a time)
- Invalid field types (string where number expected, etc.)
- Boundary values (min, max, empty string, null)
- Special characters and injection attempts

AUTHENTICATION:
- Valid token → 200
- Expired token → 401
- Invalid token → 401
- Missing token → 401
- Insufficient permissions → 403

ERROR HANDLING:
- Non-existent resource → 404
- Duplicate creation → 409
- Rate limit exceeded → 429
- Server error simulation → 500

Format each test case with:
- Request (method, URL, headers, body)
- Expected response (status code, body structure)
- Assertions to verify

Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.