Back to Case StudiesCase Study #3 of 4
TESTED BY ME•API & Backend QA•2026
Enterprise REST API Test Suite
HTTP Status Codes, Schema Validation & Boundary Injections
Automated and manual backend API testing using Postman collections to validate HTTP status codes, JSON schema structures, boundary payloads, and authentication tokens.
Endpoints Tested24
Assertions Written110
API Defects Logged7
CRUD Coverage100%
The Engineering Challenge
Unvalidated API request bodies caused internal 500 server crashes and unhandled database exceptions instead of returning appropriate 4xx client error status codes.
The QA & Dev Solution
Designed Postman collections covering 24 endpoints across GET, POST, PUT, DELETE with 110 automated assertion scripts. Tested negative boundaries, SQL injection payloads, and null parameters.
My Actual Responsibilities
- 01.Authored 110 Postman assertions verifying response schemas and latency
- 02.Validated HTTP response codes (200, 201, 400, 401, 403, 404, 409, 500)
- 03.Tested security boundary payloads including special characters and oversized strings
- 04.Documented API defect logs with cURL requests and JSON payload reproduction steps
Deliverables Produced
Exportable Postman Environment & Collection Suite
API Defect Matrix & Status Code Log
Schema Validation & Latency Audit
Technologies & Testing Utilities:
PostmanJSON Schema ValidatorcURLGitREST APIsBoundary Testing
Executed Test Scenarios Matrix
All Scenarios Verified| Test ID | Scenario / Condition | Technique | Expected Result | Result |
|---|---|---|---|---|
| TC-API-01 | POST /api/v1/auth/login - Valid credentials authentication | Positive Functional | 200 OK with Bearer Token and user metadata in JSON body | PASS |
| TC-API-02 | POST /api/v1/users - Duplicate Email Registration | Negative / Validation | 409 Conflict with informative error message: 'Email already exists' | PASS |
| TC-API-03 | DELETE /api/v1/items/999999 - Non-existent resource ID | Error Handling | 404 Not Found response instead of database crash | PASS |
BUG-API-02: POST /api/v1/users returns 500 Error when payload age is negative stringReporter: Youssef Salah Elbltagi • Software Testing Trainee @ DEPI
Severity: MediumPriority: P2 - Medium
Environment: Postman v10.22 / Staging Server API v1.2
Status: Confirmed Defect
Regression: Verified
Steps to Reproduce:
- Send POST request to `/api/v1/users`.
- Set JSON body: `{"name":"Test User", "age": "-55"}`.
- Execute request and observe response code.
Expected Result:400 Bad Request with field validation error: 'Age must be a positive integer'.
Actual Result:500 Internal Server Error with unhandled database exception stack trace in response.
Next Case Study:Dual-Engine Creative Studio Portfolio
Explore Next Project