Bird
Raised Fist0
Laravelframework~5 mins

HTTP test assertions in Laravel

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction

HTTP test assertions help you check if your web app responds correctly to requests. They make sure your app works as expected without opening a browser.

When you want to confirm a page loads successfully after a user visits it.
When you need to check if submitting a form redirects to the right page.
When you want to verify that an API returns the correct status code and data.
When you want to ensure unauthorized users get blocked from certain pages.
When you want to test that error pages show up correctly for bad requests.
Syntax
Laravel
$response->assertStatus(200);
$response->assertSee('Welcome');
$response->assertRedirect('/home');

Use $response from your HTTP test calls like $this->get() or $this->post().

Assertions check things like status codes, page content, redirects, and JSON responses.

Examples
Check that the home page loads with a 200 OK status.
Laravel
$response = $this->get('/');
$response->assertStatus(200);
Check that after login, the user is redirected to the dashboard.
Laravel
$response = $this->post('/login', ['email' => 'user@example.com', 'password' => 'secret']);
$response->assertRedirect('/dashboard');
Check that the profile page contains the text 'User Profile'.
Laravel
$response = $this->get('/profile');
$response->assertSee('User Profile');
Check that the API returns JSON with a success key set to true.
Laravel
$response = $this->getJson('/api/data');
$response->assertJson(['success' => true]);
Sample Program

This test class has two tests: one checks the home page loads with status 200 and shows a welcome message. The other checks that logging in redirects the user to the dashboard page.

Laravel
<?php

namespace Tests\Feature;

use Tests\TestCase;

class HomePageTest extends TestCase
{
    public function test_home_page_loads_successfully()
    {
        $response = $this->get('/');

        $response->assertStatus(200);
        $response->assertSee('Welcome to Our Site');
    }

    public function test_login_redirects_to_dashboard()
    {
        $response = $this->post('/login', [
            'email' => 'user@example.com',
            'password' => 'password123',
        ]);

        $response->assertRedirect('/dashboard');
    }
}
OutputSuccess
Important Notes

Always use HTTP test assertions inside your test methods after making a request.

Use assertStatus() to check HTTP codes like 200, 404, or 302.

Use assertSee() to check if certain text appears in the response body.

Summary

HTTP test assertions help confirm your app responds correctly to requests.

Common assertions include checking status codes, redirects, and page content.

They make your tests reliable and your app more stable.

Practice

(1/5)
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' => 'user@example.com', '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