Scribd
Upload
4 views2 pages

API Manual Testing Real Time Interview Questions

The document provides a comprehensive set of interview questions and answers for API manual testing, covering various scenarios such as testing without a UI, handling errors, validating responses, and ensuring security. It discusses methods for testing different types of APIs, including authentication, pagination, and file uploads, as well as performance and integration testing. Additionally, it highlights the importance of understanding status codes, API contract testing, and challenges faced during API testing.

Uploaded by

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

API Manual Testing Real Time Interview Questions

The document provides a comprehensive set of interview questions and answers for API manual testing, covering various scenarios such as testing without a UI, handling errors, validating responses, and ensuring security. It discusses methods for testing different types of APIs, including authentication, pagination, and file uploads, as well as performance and integration testing. Additionally, it highlights the importance of understanding status codes, API contract testing, and challenges faced during API testing.

Uploaded by

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

API Manual Testing Interview Questions

Real-Time Scenario Based

Q: How do you test an API without UI?


A: Use tools like Postman or Swagger to validate request, response, status codes, headers,
business logic, and database data.

Q: 200 OK but incorrect data is returned. What will you do?


A: Validate API contract, compare response with database, check request payload, and raise a
functional defect.

Q: How do you test authentication APIs?


A: Test valid and invalid credentials, token generation, expired token, missing token, and
unauthorized access.

Q: API intermittently returns 500 error. How will you debug?


A: Reproduce issue, analyze server logs, validate payload, and check dependency services.

Q: How do you validate API responses?


A: Check status code, response body, schema validation, mandatory fields, and business rules.

Q: What negative scenarios do you test?


A: Missing fields, invalid data types, boundary values, invalid headers, unauthorized access.

Q: How do you test pagination APIs?


A: Verify record count, page logic, invalid page values, and total record count.

Q: Difference between POST, PUT, and PATCH?


A: POST creates, PUT updates full resource, PATCH updates partial fields.

Q: How do you test file upload APIs?


A: Validate file format, size, empty file, and verify upload in database/storage.

Q: What is idempotency?
A: Multiple identical requests should not create duplicate records.

Q: How do you test API integration?


A: Validate data flow between APIs, failure handling, and rollback scenarios.

Q: How do you test API performance manually?


A: Check response time, large payload handling, and timeout behavior.

Q: How do you handle dynamic values in APIs?


A: Extract values from response and pass them to subsequent requests.

Q: How do you test DELETE APIs?


A: Delete existing and non-existing records and verify database updates.
Q: How do you test API security?
A: Test authentication, authorization, role access, injection attacks, and data exposure.

Q: Difference between 400, 401, 403, 404 status codes?


A: 400 – Bad Request, 401 – Unauthorized, 403 – Forbidden, 404 – Not Found.

Q: What is API contract testing?


A: Validate APIs against Swagger/OpenAPI definitions.

Q: How do you test API versioning?


A: Ensure backward compatibility between versions.

Q: Real-time challenge faced in API testing?


A: Testing backend APIs before UI readiness and identifying business logic defects.

You might also like