HTTP test assertions in Laravel - Step-by-Step Execution

Concept Flow - HTTP test assertions

Send HTTP Request

↓

Receive HTTP Response

↓

Check Status Code

↓

Check Response Content

↓

Assert Expected Result

↓

PASS/FAIL

This flow shows how Laravel sends an HTTP request, receives a response, and then checks assertions like status code and content to decide if the test passes.

Execution Sample

Laravel

public function test_homepage()
{
    $response = $this->get('/');
    $response->assertStatus(200);
    $response->assertSee('Welcome');
}

This test sends a GET request to '/' and asserts the response status is 200 and the page contains 'Welcome'.

Execution Table

Step	Action	Evaluation	Result
1	Send GET request to '/'	Request sent	Response received
2	Check status code == 200	Status is 200	Pass
3	Check response contains 'Welcome'	'Welcome' found	Pass
4	All assertions passed	Test passes	PASS

💡 Test ends after all assertions pass successfully.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
$response	null	HTTP response object	Same	Same	Same
Status Code	N/A	N/A	200	200	200
Response Content	N/A	N/A	N/A	Contains 'Welcome'	Contains 'Welcome'

Key Moments - 2 Insights

Why does assertStatus(200) come before assertSee('Welcome')?

Because checking the status code first ensures the response is valid before looking for content, as shown in steps 2 and 3 of the execution_table.

What happens if the status code is not 200?

The test fails immediately at step 2, so assertSee is not checked, preventing misleading errors.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of step 3?

A Fail

B Skipped

C Pass

D Error

💡 Hint

Check the 'Result' column for step 3 in the execution_table.

At which step does the test confirm the HTTP status code?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Action' column in the execution_table for status code check.

If the response did not contain 'Welcome', which step would fail?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Refer to the 'Action' and 'Result' columns in the execution_table for content check.

Concept Snapshot

Laravel HTTP test assertions:
- Use $this->get('/url') to send request
- Use assertStatus(code) to check HTTP status
- Use assertSee(text) to check response content
- Assertions run in order; failure stops test
- Helps verify your app responds correctly

Full Transcript

In Laravel HTTP test assertions, you send a request using methods like get(). Then you check the response status with assertStatus(). Next, you check if the response contains expected text with assertSee(). The test passes only if all assertions succeed in order. If any assertion fails, the test stops immediately. This helps ensure your web app behaves as expected when accessed.

Practice

1. Which Laravel HTTP test assertion checks if the response status code is 200?

easy

A. $response->assertStatus(200);

B. $response->assertRedirect('/home');

C. $response->assertSee('Welcome');

D. $response->assertJson(['success' => true]);

Solution

1. Step 1: Understand the purpose of assertStatus

   This method checks the HTTP status code returned by the response.

2. Step 2: Match the status code 200 with the assertion

   $response->assertStatus(200); confirms the response was successful (OK).

3. Final Answer:

   $response->assertStatus(200); -> Option A

4. Quick Check:

   Check status code = assertStatus(200) [OK]

Hint: Use assertStatus(200) to check for OK response quickly [OK]

Common Mistakes:

• Confusing assertRedirect with assertStatus
• Using assertSee to check status code
• Expecting assertJson to check status

2. Which of the following is the correct syntax to assert a redirect to the URL '/dashboard' in a Laravel HTTP test?

easy

A. $response->assertLocation('/dashboard', 200);

B. $response->redirect('/dashboard');

C. $response->assertRedirect('/dashboard');

D. $response->assertStatus(302, '/dashboard');

Solution

1. Step 1: Identify the correct assertion method for redirects

   Laravel uses assertRedirect() to check if the response redirects to a given URL.

2. Step 2: Confirm the syntax matches the method signature

   The correct syntax is $response->assertRedirect('/dashboard'); which asserts a redirect to '/dashboard'.

3. Final Answer:

   $response->assertRedirect('/dashboard'); -> Option C

4. Quick Check:

   Redirect assertion = assertRedirect(url) [OK]

Hint: Use assertRedirect('url') to check redirects in tests [OK]

Common Mistakes:

• Using assertStatus with URL parameter
• Calling redirect() instead of assertRedirect()
• Using assertLocation with incorrect status code

3. Given the following test code:

$response = $this->get('/welcome');
$response->assertStatus(200);
$response->assertSee('Hello World');

What will happen if the page '/welcome' returns status 404?

medium

A. The test will fail on assertSee because the content is missing.

B. The test will pass because assertSee ignores status codes.

C. The test will throw a syntax error.

D. The test will fail on assertStatus(200) because the status is 404.

Solution

1. Step 1: Analyze the response status code

   The response returns 404, which means 'Not Found', not 200.

2. Step 2: Understand the effect of assertStatus(200)

   This assertion expects a 200 status code, so it will fail when the actual status is 404.

3. Final Answer:

   The test will fail on assertStatus(200) because the status is 404. -> Option D

4. Quick Check:

   Status mismatch causes assertStatus failure [OK]

Hint: Check status code first; assertStatus fails if codes differ [OK]

Common Mistakes:

• Assuming assertSee passes regardless of status
• Expecting syntax errors from valid code
• Ignoring the importance of status code in tests

4. You wrote this test:

$response = $this->post('/login', ['email' => '[e-mail]', 'password' => 'secret']);
$response->assertRedirect('/dashboard');
$response->assertStatus(200);

Why does this test fail even though the redirect is correct?

medium

A. Because the post method should be get for redirects.

B. Because assertStatus(200) conflicts with the redirect status code 302.

C. Because the URL '/dashboard' is incorrect.

D. Because assertRedirect must come after assertStatus.

Solution

1. Step 1: Understand HTTP redirect status codes

   Redirect responses usually have status code 302, not 200.

2. Step 2: Check the conflict between assertions

   assertRedirect('/dashboard') expects a 302 status, but assertStatus(200) expects 200, causing failure.

3. Final Answer:

   Because assertStatus(200) conflicts with the redirect status code 302. -> Option B

4. Quick Check:

   Redirect status is 302, not 200 [OK]

Hint: Redirects use 302 status; don't assert 200 with assertRedirect [OK]

Common Mistakes:

• Mixing HTTP methods for redirect tests
• Assuming assertRedirect changes status code
• Thinking assertion order affects results

5. You want to test that a JSON API response contains a key 'status' with value 'success' and also returns HTTP status 201. Which assertion combination is correct?

hard

A. $response->assertStatus(201)->assertJson(['status' => 'success']);

B. $response->assertJson(['status' => 'success'])->assertRedirect(201);

C. $response->assertStatus(200)->assertJson(['status' => 'success']);

D. $response->assertSee('success')->assertStatus(201);

Solution

1. Step 1: Identify the correct status code assertion

   HTTP 201 means 'Created', so assertStatus(201) is needed.

2. Step 2: Use assertJson to check JSON content

   assertJson(['status' => 'success']) verifies the JSON key and value.

3. Step 3: Combine assertions correctly

   Chaining assertStatus(201) and assertJson([...]) is valid and checks both conditions.

4. Final Answer:

   $response->assertStatus(201)->assertJson(['status' => 'success']); -> Option A

5. Quick Check:

   Status 201 + JSON key check = assertStatus + assertJson [OK]

Hint: Chain assertStatus(201) with assertJson for API success checks [OK]

Common Mistakes:

• Using assertRedirect with status code
• Checking status 200 instead of 201
• Using assertSee for JSON content