Integration testing in Rest API - Step-by-Step Execution

Concept Flow - Integration testing

Write individual modules

↓

Develop integration tests

↓

Run integration tests

↓

Check if modules work together

↓

Deploy

Integration testing checks if different parts of a program work well together by running tests that combine modules.

Execution Sample

Rest API

POST /login {"user":"alice","pass":"123"}
GET /profile (with token)
Assert profile data correct

This test sends a login request, then uses the returned token to get the profile, checking if the data matches expected.

Execution Table

Step	Action	Request Sent	Response Received	Check	Result
1	Send login request	POST /login {"user":"alice","pass":"123"}	{"token":"abc123"}	Token received?	Pass
2	Send profile request with token	GET /profile Authorization: Bearer abc123	{"name":"Alice","email":"[e-mail]"}	Profile data correct?	Pass
3	Integration test result	-	-	All steps passed?	Pass

💡 All integration steps passed, modules work together correctly.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
token	None	"abc123"	"abc123"	"abc123"
profile_data	None	None	{"name":"Alice","email":"[e-mail]"}	{"name":"Alice","email":"[e-mail]"}

Key Moments - 2 Insights

Why do we need to use the token from the login response in the profile request?

Because the profile endpoint requires authentication, the token proves the user is logged in. See execution_table step 2 where the token is sent.

What happens if the profile data does not match expected?

The integration test fails at step 2, indicating modules do not work together properly and need fixing before deployment.

Visual Quiz - 3 Questions

Look at the execution table, what is the token value after step 1?

A "xyz789"

B "abc123"

C None

D "token"

💡 Hint

Check the 'Response Received' column in step 1 of the execution_table.

At which step does the test check if profile data is correct?

A Step 2

B Step 1

C Step 3

D No step checks profile data

💡 Hint

Look at the 'Check' column in the execution_table.

If the login response did not return a token, what would happen in the execution table?

A Step 3 would say Pass

B Step 2 would pass anyway

C Step 1 result would be Fail

D No change in the table

💡 Hint

Refer to the 'Result' column in step 1 of the execution_table.

Concept Snapshot

Integration testing combines multiple modules to test them working together.
Write tests that send real requests between modules.
Check responses and data flow between parts.
Fail tests if modules don't cooperate correctly.
Fix issues before deploying the whole system.

Full Transcript

Integration testing is the process of checking if different parts of a program work well together. First, individual modules are written. Then, integration tests are developed that send requests combining these modules. For example, a login request is sent, and the returned token is used to request a user profile. The test checks if the profile data matches what is expected. If all steps pass, the modules work together correctly and the system can be deployed. If any step fails, the problem must be fixed and tests rerun. This ensures the whole system functions as intended.