Database testing (RefreshDatabase) in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to use the RefreshDatabase trait in a Laravel test class.

Laravel

<?php

namespace Tests\Feature;

use Illuminate\Foundation\Testing\[1];
use Tests\TestCase;

class UserTest extends TestCase
{
    use RefreshDatabase;

    public function test_example()
    {
        $this->assertTrue(true);
    }
}

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

ADatabaseMigrations

BWithoutMiddleware

CWithFaker

DRefreshDatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Using DatabaseMigrations instead of RefreshDatabase

Forgetting to import the trait

Not using any trait to reset the database

The RefreshDatabase trait resets the database after each test, ensuring a clean state.

2fill in blank

medium

Complete the code to run a test that checks if a user record exists after creation.

Laravel

public function test_user_creation()
{
    \App\Models\User::factory()->create();

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

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

Ausers

Buser

Caccounts

Dprofiles

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular 'user' instead of 'users'

Using unrelated table names like 'accounts' or 'profiles'

The assertDatabaseHas method checks the users table for the given data.

3fill in blank

hard

Fix the error in the test method to correctly refresh the database before running.

Laravel

public function test_database_refresh()
{
    $this->[1]();
    $this->assertTrue(true);
}

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

AmigrateRefresh

BrefreshDatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect method names like migrateRefresh

Calling refreshDatabase manually instead of using the trait

The correct method to refresh the database in a test is refreshDatabase(), but it is not a method you call manually. Instead, you use the RefreshDatabase trait. This question expects the learner to recognize the correct method name if called.

4fill in blank

hard

Fill both blanks to correctly import and use the RefreshDatabase trait in a Laravel test.

Laravel

<?php

namespace Tests\Unit;

use Illuminate\Foundation\Testing\[1];
use Tests\TestCase;

class ProductTest extends TestCase
{
    use [2];

    public function test_product_creation()
    {
        $this->assertTrue(true);
    }
}

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

ARefreshDatabase

BDatabaseMigrations

DWithFaker

Attempts:

3 left

💡 Hint

Common Mistakes

Importing one trait but using another

Forgetting to use the trait inside the class

You must import RefreshDatabase and then use it inside the class to refresh the database between tests.

5fill in blank

hard

Fill all three blanks to write a test that creates a user and asserts the database has the user email.

Laravel

public function test_user_database_entry()
{
    $user = \App\Models\User::factory()->create();

    $this->assertDatabaseHas([1], [
        [2] => [3],
    ]);
}

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

A'users'

B'email'

C'[e-mail]'

D'name'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong table name or missing quotes

Using wrong column name

Using a value that does not match the created user

The assertDatabaseHas method checks the 'users' table for a record where 'email' equals '[e-mail]'.

Practice

1. What is the main purpose of using the RefreshDatabase trait in Laravel tests?

easy

A. To seed the database with test data before tests run

B. To speed up tests by skipping database migrations

C. To reset the database after each test to ensure a clean state

D. To backup the database before running tests

Solution

1. Step 1: Understand the role of RefreshDatabase

   The trait resets the database by running migrations fresh for each test.

2. Step 2: Identify why resetting is important

   Resetting ensures tests do not affect each other by leftover data.

3. Final Answer:

   To reset the database after each test to ensure a clean state -> Option C

4. Quick Check:

   Database reset = Clean test state [OK]

Hint: Remember: RefreshDatabase cleans database for every test [OK]

Common Mistakes:

• Thinking it seeds data automatically
• Confusing it with speeding up tests
• Assuming it backs up data

2. Which of the following is the correct way to use RefreshDatabase in a Laravel test class?

easy

A. class ExampleTest extends TestCase { implements RefreshDatabase }

B. class ExampleTest extends TestCase { RefreshDatabase(); }

C. class ExampleTest extends TestCase { @RefreshDatabase }

D. class ExampleTest extends TestCase { use RefreshDatabase; }

Solution

1. Step 1: Recall trait usage syntax in PHP

   Traits are included using the use keyword inside the class body.

2. Step 2: Match syntax with options

   Only class ExampleTest extends TestCase { use RefreshDatabase; } correctly uses use RefreshDatabase; inside the class.

3. Final Answer:

   class ExampleTest extends TestCase { use RefreshDatabase; } -> Option D

4. Quick Check:

   Traits use use keyword inside class [OK]

Hint: Traits use 'use' keyword inside class body [OK]

Common Mistakes:

• Using parentheses like a method call
• Using annotations instead of traits
• Trying to implement traits as interfaces

3. Given this Laravel test code snippet using RefreshDatabase:

public function test_user_creation() {
    User::factory()->create(['name' => 'Alice']);
    $this->assertDatabaseHas('users', ['name' => 'Alice']);
}

What will happen if you run this test twice in a row?

medium

A. Both tests pass because the database is reset each time

B. The second test fails due to duplicate user entries

C. Both tests fail because the database is not migrated

D. The first test passes, second test errors out with connection issue

Solution

1. Step 1: Understand RefreshDatabase effect

   It resets the database before each test, so no leftover data remains.

2. Step 2: Analyze test behavior on repeated runs

   Each test run starts fresh, so creating 'Alice' user and asserting passes every time.

3. Final Answer:

   Both tests pass because the database is reset each time -> Option A

4. Quick Check:

   Database reset = independent test runs [OK]

Hint: RefreshDatabase resets DB so repeated tests stay clean [OK]

Common Mistakes:

• Assuming data persists between tests
• Thinking duplicate entries cause failure
• Confusing RefreshDatabase with no migration

4. You wrote a Laravel test using RefreshDatabase but the database is not resetting between tests. What is the most likely cause?

medium

A. You did not call migrate:fresh manually before tests

B. You forgot to add use RefreshDatabase; trait in your test class

C. You used RefreshDatabase but did not seed the database

D. You ran tests without the --database option

Solution

1. Step 1: Check trait usage in test class

   Without adding use RefreshDatabase;, the trait's reset logic won't run.

2. Step 2: Understand that manual migration commands are not needed

   The trait handles migrations automatically; manual commands are unnecessary.

3. Final Answer:

   You forgot to add use RefreshDatabase; trait in your test class -> Option B

4. Quick Check:

   Trait must be included to reset DB [OK]

Hint: Always add trait with 'use RefreshDatabase;' inside test class [OK]

Common Mistakes:

• Thinking manual migration commands are required
• Confusing seeding with resetting
• Assuming command line options affect trait behavior

5. You want to write a Laravel test that uses RefreshDatabase but also seeds some initial data before each test. Which approach is correct?

hard

A. Use RefreshDatabase trait and call $this->seed() in the test's setUp() method

B. Use RefreshDatabase trait and add seeder class name as a parameter to the trait

C. Manually run php artisan migrate:fresh --seed before running tests

D. Use RefreshDatabase trait and override the refreshDatabase() method to seed

Solution

1. Step 1: Understand how to seed with RefreshDatabase

   The trait resets the database, but seeding must be triggered manually in tests.

2. Step 2: Use $this->seed() in setUp() method

   This ensures seeding runs before each test after database reset.

3. Final Answer:

   Use RefreshDatabase trait and call $this->seed() in the test's setUp() method -> Option A

4. Quick Check:

   Seed manually after refresh in setUp() [OK]

Hint: Call $this->seed() in setUp() when using RefreshDatabase [OK]

Common Mistakes:

• Trying to pass seeder to trait directly
• Running artisan commands manually during tests
• Overriding trait methods unnecessarily