Feature tests in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a basic feature test class in Laravel.

Laravel

<?php

namespace Tests\Feature;

use Tests\TestCase;

class ExampleTest extends TestCase
{
    public function test_basic_example()
    {
        $response = $this->[1]('/');

        $response->assertStatus(200);
    }
}

Drag options to blanks, or click blank then click option'

Aget

Bpost

Cput

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST instead of GET for a simple page request.

Confusing HTTP verbs in the test method.

The get method sends a GET request to the given URL, which is common for basic feature tests.

2fill in blank

medium

Complete the code to assert that the response contains the text 'Welcome'.

Laravel

$response = $this->get('/home');
$response->[1]('Welcome');

Drag options to blanks, or click blank then click option'

AassertRedirect

BassertJson

CassertSeeText

DassertStatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using assertJson when the response is HTML.

Using assertRedirect instead of checking content.

assertSeeText checks if the response contains the given plain text.

3fill in blank

hard

Fix the error in the test method to correctly test a POST request with data.

Laravel

public function test_submit_form()
{
    $response = $this->post('/submit', [1]);
    $response->assertStatus(302);
}

Drag options to blanks, or click blank then click option'

A['John', '[e-mail]']

B'name=John&email=[e-mail]'

Cnull

D['name' => 'John', 'email' => '[e-mail]']

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a query string instead of an array.

Passing null or a list without keys.

The POST data must be an associative array with keys matching form fields.

4fill in blank

hard

Fill both blanks to test that a user is authenticated and redirected after login.

Laravel

public function test_user_login()
{
    $user = User::factory()->create();

    $response = $this->post('/login', ['email' => $user->email, 'password' => 'password']);

    $response->assertRedirect([1]);
    $this->assertAuthenticatedAs([2]);
}

Drag options to blanks, or click blank then click option'

A'/dashboard'

B$user

C'/home'

Dauth()->user()

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong redirect URL.

Checking authentication against a wrong user variable.

The test expects a redirect to '/dashboard' and checks the authenticated user matches the created user.

5fill in blank

hard

Fill all three blanks to create a feature test that checks JSON response structure and status.

Laravel

public function test_api_response()
{
    $response = $this->json([1], '/api/data');

    $response->assertStatus([2])
             ->assertJsonStructure([3]);
}

Drag options to blanks, or click blank then click option'

A'GET'

B200

C['data', 'meta']

D'POST'

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST instead of GET for fetching data.

Expecting wrong status code.

Checking incorrect JSON keys.

The test sends a GET JSON request, expects HTTP 200 status, and checks the JSON has 'data' and 'meta' keys.

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