Feature tests in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does this Laravel feature test do?

Consider this Laravel feature test code. What is the expected behavior when this test runs?

Laravel

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

A It checks that the homepage URL returns a 200 status and contains the text 'Welcome to our site'.

B It tests that the homepage redirects to another page with a welcome message.

C It ensures the homepage returns JSON data containing a welcome message.

D It verifies that the homepage returns a 404 error with a welcome message.

💡 Hint

Look at the methods get(), assertStatus(), and assertSee() to understand what is tested.

The test sends a GET request to '/' and expects a 200 OK status. It also checks that the response contains the text 'Welcome to our site'.

📝 Syntax

intermediate

Identify the syntax error in this Laravel feature test

Which option correctly fixes the syntax error in this test method?

Laravel

public function test_user_can_login()
{
    $response = $this->post('/login', [
        'email' => '[e-mail]',
        'password' => 'secret'
    ]);
    $response->assertRedirect('/dashboard');
}

A Change post() to get() to fix the syntax error.

B Remove the closing brace '}' to fix the syntax error.

C Add a semicolon after assertRedirect('/dashboard') to fix the syntax error.

D Replace the array with a JSON string to fix the syntax error.

💡 Hint

Check the end of the assertRedirect line for missing punctuation.

The missing semicolon after the assertRedirect() call causes a syntax error. Adding it fixes the problem.

❓ state_output

advanced

What is the state of the database after this feature test runs?

Given this Laravel feature test that creates a user, what will be the number of users in the database after the test completes?

Laravel

public function test_user_creation()
{
    $this->post('/users', [
        'name' => 'Alice',
        'email' => '[e-mail]',
        'password' => 'password123'
    ]);

    $this->assertDatabaseHas('users', ['email' => '[e-mail]']);
}

A The test will fail because the password is not hashed.

B There will be multiple users with the same email due to repeated test runs.

C There will be exactly one user with email '[e-mail]' in the users table.

D There will be no users in the database because tests do not persist data.

💡 Hint

Laravel feature tests use database transactions by default to isolate tests.

Laravel feature tests wrap each test in a database transaction that is rolled back after the test completes, ensuring test isolation and no persistent data changes.

🔧 Debug

advanced

Why does this Laravel feature test fail?

This test is supposed to check that a guest user is redirected to login when accessing /dashboard. Why does it fail?

Laravel

public function test_guest_redirected_to_login()
{
    $response = $this->get('/dashboard');
    $response->assertStatus(200);
    $response->assertSee('Login');
}

A The test fails because the /dashboard route does not exist.

B The test expects status 200 but the route redirects with status 302, causing failure.

C The test fails because the response does not contain the word 'Login'.

D The test fails because the get() method requires authentication.

💡 Hint

Check the expected HTTP status code for redirects.

Guests accessing /dashboard are redirected to login with a 302 status. The test expects 200, so it fails.

🧠 Conceptual

expert

Which option best describes Laravel feature tests?

Choose the statement that correctly explains the purpose and behavior of Laravel feature tests.

A Feature tests simulate user interactions with the application through HTTP requests to verify end-to-end behavior.

B Feature tests only check individual methods in models without involving HTTP requests.

C Feature tests are used to test database migrations and schema changes only.

D Feature tests run in production to monitor live user activity.

💡 Hint

Think about what 'feature' means in testing Laravel apps.

Feature tests simulate real user actions by sending HTTP requests and checking responses, covering multiple layers.

Practice

1. What is the main purpose of Feature tests in Laravel?

easy

A. To test how the application behaves from the user's perspective

B. To check the syntax of PHP code

C. To test database migrations only

D. To optimize application performance

Solution

1. Step 1: Understand the role of feature tests

   Feature tests simulate user actions and check the app's responses to ensure it works as expected.

2. Step 2: Compare with other test types

   Unlike unit tests or migration tests, feature tests focus on user experience and request handling.

3. Final Answer:

   To test how the application behaves from the user's perspective -> Option A

4. Quick Check:

   Feature tests = user behavior testing [OK]

Hint: Feature tests simulate user requests and responses [OK]

Common Mistakes:

• Confusing feature tests with unit tests
• Thinking feature tests only check database
• Assuming feature tests optimize performance

2. Which of the following is the correct way to start a feature test method in Laravel?

easy

A. public testUserCanLogin()

B. function testUserCanLogin()

C. public function testUserCanLogin()

D. def testUserCanLogin()

Solution

1. Step 1: Recall Laravel test method syntax

   Laravel feature test methods must be public and start with 'test' or have the @test annotation.

2. Step 2: Identify correct PHP method declaration

   Only 'public function testUserCanLogin()' is valid PHP syntax for a test method in Laravel.

3. Final Answer:

   public function testUserCanLogin() -> Option C

4. Quick Check:

   Test methods are public functions [OK]

Hint: Test methods must be public functions starting with 'test' [OK]

Common Mistakes:

• Omitting 'public' keyword
• Using wrong function declaration syntax
• Using Python style 'def' keyword

3. Given this Laravel feature test code:

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

What does this test check?

medium

A. The home page returns a 404 error

B. The home page returns a 200 OK status

C. The home page redirects to login

D. The home page returns JSON data

Solution

1. Step 1: Analyze the HTTP request in the test

   The test sends a GET request to '/' (home page).

2. Step 2: Check the assertion

   The test asserts the response status is 200, meaning OK.

3. Final Answer:

   The home page returns a 200 OK status -> Option B

4. Quick Check:

   assertStatus(200) means success [OK]

Hint: assertStatus(200) means page loaded successfully [OK]

Common Mistakes:

• Confusing 200 with 404 or redirect codes
• Assuming JSON response without checking
• Misreading the URL path

4. What is wrong with this Laravel feature test code?

public function testUserRegistration()
{
    $response = $this->post('/register', [
        'email' => '[e-mail]',
        'password' => 'secret',
    ]);
    $response->assertRedirect('/home');
}

medium

A. Missing CSRF token in the post request

B. Password should be hashed before sending

C. Password field should be 'password_confirmation' instead of 'password'

D. The test method is missing the 'public' keyword

Solution

1. Step 1: Understand Laravel's CSRF protection

   Laravel requires a CSRF token for POST requests to prevent attacks.

2. Step 2: Check test request handling

   Feature tests use the 'web' middleware group by default, which includes CSRF protection. The $this->post() method does not automatically include a CSRF token, so the test will fail unless the token is provided or middleware is disabled.

3. Step 3: Identify the actual issue

   Since the test does not disable middleware, missing CSRF token causes failure.

4. Final Answer:

   Missing CSRF token in the post request -> Option A

5. Quick Check:

   POST requests need CSRF token unless middleware disabled [OK]

Hint: Remember CSRF token is needed for POST requests [OK]

Common Mistakes:

• Assuming password must be hashed in test input
• Confusing password and password_confirmation fields
• Ignoring middleware effects on tests

5. You want to test a feature where a logged-in user can update their profile. Which sequence correctly sets up the test in Laravel feature tests?

hard

A. Assert redirect -> Create user -> Send POST request -> Act as user

B. Send POST request to update route -> Create user -> Assert redirect -> Act as user

C. Act as user -> Assert redirect -> Create user -> Send POST request

D. Create user -> Act as user -> Send POST request to update route -> Assert redirect

Solution

1. Step 1: Create a user to simulate logged-in state

   First, create a user instance in the database for authentication.

2. Step 2: Use actingAs() to simulate logged-in user

   Use $this->actingAs($user) to run requests as that user.

3. Step 3: Send POST request to update profile route

   Send the update request while acting as the user.

4. Step 4: Assert the response redirects as expected

   Check that the response redirects to the correct page after update.

5. Final Answer:

   Create user -> Act as user -> Send POST request to update route -> Assert redirect -> Option D

6. Quick Check:

   Setup user then act as user before request [OK]

Hint: Create user first, then act as user before request [OK]

Common Mistakes:

• Sending request before acting as user
• Not creating user before acting as user
• Asserting redirect before sending request