API API Error Handling and Debugging 3

Question 1

What does 'negative testing' mean in API testing?

Accepted Answer

Sending invalid or unexpected inputs to verify the API handles errors gracefully

Answer

Testing APIs expected to fail permanently

Answer

Testing with no authentication

Answer

Measuring negative performance metrics

Question 2

What is 'boundary value testing' in API test design?

Accepted Answer

Testing at the minimum and maximum allowed input values

Answer

Testing API network boundaries

Answer

Testing cross-region APIs

Answer

Testing rate limit boundaries only

Question 3

What does the Retry-After header tell an API client?

Accepted Answer

How long to wait before making another request after a rate limit or 503

Answer

When the API was last updated

Answer

The time the request was received

Answer

The server's uptime

Question 4

What is 'fault injection testing' for APIs?

Accepted Answer

Deliberately introducing failures to verify the system's resilience and error handling

Answer

Testing with corrupted hardware

Answer

Injecting test data into the API

Answer

SQL injection security testing

Question 5

What does a 429 Too Many Requests response indicate?

Accepted Answer

The client has exceeded the API rate limit

Answer

Database query limit reached

Answer

Too many parameters in the request

Answer

Server memory limit hit

Question 6

What is 'logging' in API error debugging and why is it important?

Accepted Answer

Recording request/response details and errors to trace and diagnose issues

Answer

Writing API documentation

Answer

Storing API credentials

Answer

Archiving old API versions