Scribd
Upload
3 views1 page

API Testing Guide: Postman & Manual Plan

The document outlines a manual API testing plan using Postman for user management endpoints, detailing expected responses and tests for each endpoint. It includes suggested requests for listing, retrieving, creating, updating, and deleting users, along with specific validation checks and automation instructions using Newman. Additionally, it provides sample assertions for schema validation and response header checks.

Uploaded by

Dangeti Sathibabu
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views1 page

API Testing Guide: Postman & Manual Plan

The document outlines a manual API testing plan using Postman for user management endpoints, detailing expected responses and tests for each endpoint. It includes suggested requests for listing, retrieving, creating, updating, and deleting users, along with specific validation checks and automation instructions using Newman. Additionally, it provides sample assertions for schema validation and response header checks.

Uploaded by

Dangeti Sathibabu
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

API Testing — Postman / Manual plan

Endpoints (JSON server typical)

 GET /users — list users

 GET /users/:id — get user

 POST /users — create user

 PUT /users/:id or PATCH /users/:id — update user

 DELETE /users/:id — delete user

Postman collection outline (suggested requests)

1. GET /users — expect 200, JSON array

o Tests: response time <500ms, schema: array of objects with id, name, email, role

2. GET /users/1 — expect 200 for existing id, 404 for non-existing id

3. POST /users — valid body → expect 201 and returned resource includes id

o Body schema: { "name": "string", "email": "string", "role": "string" }

o Tests: invalid email → 400; missing required → 400

4. PUT /users/:id — replace user; expect 200

5. PATCH /users/:id — partial update; expect 200

6. DELETE /users/:id — expect 200 or 204, then GET returns 404

Postman test scripts (examples)

 After POST: test that [Link]().email === [Link]

 After DELETE: follow-up GET expect 404

Automation / CI

 Export collection JSON and run with Newman:

o newman run UserManagement.postman_collection.json -e [Link] --reporters


cli,junit --reporter-junit-export [Link]

Sample assertions to include

 Schema validation (use ajv or Postman tests)

 Check response headers (CORS, content-type)

 Verify proper status codes on erroneous inputs (400/404/500)

You might also like