Why testing validates contracts in Rest API - Performance Analysis

Time Complexity: Why testing validates contracts

O(n)

Understanding Time Complexity

When testing REST APIs, we want to see how the time to check the contract grows as the API or tests get bigger.

We ask: How does the testing effort increase when the API has more endpoints or rules?

Scenario Under Consideration

Analyze the time complexity of the following test code snippet.

for endpoint in api_endpoints:
    response = call_api(endpoint)
    assert response.status == expected_status[endpoint]
    assert response.body matches expected_schema[endpoint]

This code tests each API endpoint by calling it and checking if the response matches the expected contract.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping over each API endpoint to test it.
• How many times: Once for each endpoint in the API.

How Execution Grows With Input

As the number of API endpoints grows, the number of tests grows the same way.

Input Size (n)	Approx. Operations
10	10 calls and checks
100	100 calls and checks
1000	1000 calls and checks

Pattern observation: The testing work grows directly with the number of endpoints.

Final Time Complexity

Time Complexity: O(n)

This means testing time grows in a straight line as the API gets bigger.

Common Mistake

[X] Wrong: "Testing one endpoint is enough to prove the whole API works."

[OK] Correct: Each endpoint can behave differently, so testing all is needed to fully check the contract.

Interview Connect

Understanding how testing scales with API size shows you can plan and write tests that keep quality as projects grow.

Self-Check

"What if we added nested loops to test multiple input cases per endpoint? How would the time complexity change?"

Practice

1. Why is testing important for validating REST API contracts?

easy

A. It makes the API run faster by optimizing code.

B. It automatically generates API documentation.

C. It ensures the API follows agreed rules and behaves as expected.

D. It replaces the need for API design.

Solution

1. Step 1: Understand the purpose of API contracts

   API contracts define rules about how APIs should behave and what data they exchange.

2. Step 2: Role of testing in contracts

   Testing checks if the API follows these rules and returns expected results, catching mistakes early.

3. Final Answer:

   It ensures the API follows agreed rules and behaves as expected. -> Option C

4. Quick Check:

   Testing validates contracts = Ensures API rules followed [OK]

Hint: Testing checks if API follows rules and returns expected data [OK]

Common Mistakes:

• Thinking testing speeds up API automatically
• Confusing testing with documentation generation
• Believing testing replaces API design

2. Which of the following is the correct way to test a REST API contract for a GET request?

easy

A. Send a DELETE request and expect a 500 error.

B. Send a POST request and check if the response status is 404.

C. Send a GET request and ignore the response content.

D. Send a GET request and check if the response status is 200 and data format matches the contract.

Solution

1. Step 1: Identify correct HTTP method and expected response

   For a GET request, the API should return status 200 and data matching the contract.

2. Step 2: Match testing action to contract validation

   Sending GET and checking status 200 plus data format confirms contract adherence.

3. Final Answer:

   Send a GET request and check if the response status is 200 and data format matches the contract. -> Option D

4. Quick Check:

   GET test checks status 200 and data format [OK]

Hint: Test GET by checking status 200 and correct data format [OK]

Common Mistakes:

• Using wrong HTTP method for the test
• Ignoring response content in tests
• Expecting error codes for successful GET

3. Given this test code snippet for a REST API endpoint:

response = client.get('/users/123')
assert response.status_code == 200
assert 'id' in response.json()
assert response.json()['id'] == 123

What does this test validate about the API contract?

medium

A. The API returns status 200 and correct user id in JSON response.

B. The API returns status 404 for missing users.

C. The API accepts POST requests at /users/123.

D. The API returns an empty JSON response.

Solution

1. Step 1: Analyze the test assertions

   The test checks that the response status code is 200 and the JSON response contains an 'id' key equal to 123.

2. Step 2: Understand what this means for the API contract

   This confirms the API returns successful status and correct user data as per contract.

3. Final Answer:

   The API returns status 200 and correct user id in JSON response. -> Option A

4. Quick Check:

   Test checks status 200 and user id = 123 [OK]

Hint: Check status and key-value in JSON to validate contract [OK]

Common Mistakes:

• Confusing status 404 with 200
• Assuming POST method is tested here
• Ignoring JSON content checks

4. A test for a REST API endpoint expects a JSON response with a 'name' field. The test code is:

response = client.get('/items/5')
assert response.status_code == 200
assert 'name' in response.json()

But the test fails with a KeyError. What is the likely cause?

medium

A. The response status code is not 200.

B. The API response JSON does not include the 'name' field as per contract.

C. The test used the wrong HTTP method.

D. The client.get() method is not defined.

Solution

1. Step 1: Understand the test failure

   A KeyError means the 'name' key is missing in the JSON response.

2. Step 2: Identify contract violation

   The API response does not include the expected 'name' field, violating the contract.

3. Final Answer:

   The API response JSON does not include the 'name' field as per contract. -> Option B

4. Quick Check:

   Missing 'name' key causes KeyError [OK]

Hint: KeyError means expected JSON key missing in response [OK]

Common Mistakes:

• Assuming wrong HTTP method caused error
• Ignoring status code correctness
• Blaming client.get() method existence

5. You have a REST API contract that requires the endpoint /orders/{id} to return a JSON with fields id, status, and items (a list). Which test best validates this contract?

hard

A. Send GET /orders/10, check status 200, verify JSON has 'id', 'status', and 'items' keys, and 'items' is a list.

B. Send POST /orders with empty body and expect status 201.

C. Send GET /orders/10 and check only the status code is 404.

D. Send DELETE /orders/10 and expect status 500.

Solution

1. Step 1: Identify contract requirements

   The contract requires GET /orders/{id} to return JSON with 'id', 'status', and 'items' keys, where 'items' is a list.

2. Step 2: Match test to contract validation

   Sending GET /orders/10, checking status 200, verifying JSON has 'id', 'status', and 'items' keys, and confirming 'items' is a list fully validates the contract.

3. Final Answer:

   Send GET /orders/10, check status 200, verify JSON has 'id', 'status', and 'items' keys, and 'items' is a list. -> Option A

4. Quick Check:

   Test checks all required fields and types [OK]

Hint: Check all required fields and data types in JSON response [OK]

Common Mistakes:

• Testing wrong HTTP method
• Ignoring required JSON fields
• Not verifying data types like list