Database testing (RefreshDatabase) in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when using RefreshDatabase trait in Laravel tests?

In Laravel, when you use the RefreshDatabase trait in your test class, what is the expected behavior regarding the database state before each test?

A The database is migrated fresh before each test, ensuring a clean state.

B The database is only migrated once before all tests run, then reused.

C The database is not touched; tests run on the existing data.

D The database is backed up before tests and restored after all tests finish.

💡 Hint

Think about how Laravel ensures tests don't affect each other with database changes.

The RefreshDatabase trait runs the migrations fresh before each test, so every test starts with a clean database. This prevents data from one test affecting another.

❓ state_output

intermediate

What is the database state after a test using RefreshDatabase completes?

If a Laravel test uses the RefreshDatabase trait and inserts a record during the test, what will be the state of the database after the test finishes?

A The inserted record is removed; the database is reset to empty or migrated state.

B The database is backed up with the inserted record for later use.

C The database is partially reset, keeping some tables intact.

D The inserted record remains in the database for the next test.

💡 Hint

Consider how RefreshDatabase affects test isolation.

After each test, the database is refreshed, so any data inserted during the test is removed. This keeps tests independent and repeatable.

📝 Syntax

advanced

Identify the correct way to use RefreshDatabase in a Laravel test class

Which of the following code snippets correctly applies the RefreshDatabase trait in a Laravel test class?

A class UserTest extends TestCase { public function testExample() { use RefreshDatabase; /* test code */ } }

B class UserTest extends TestCase { use RefreshDatabase; public function testExample() { /* test code */ } }

C class UserTest extends TestCase { public function testExample() { RefreshDatabase(); /* test code */ } }

D class UserTest extends TestCase { use RefreshDatabase(); public function testExample() { /* test code */ } }

💡 Hint

Remember how traits are included in PHP classes.

Traits in PHP are included using the use keyword inside the class body, not inside methods or with parentheses.

🔧 Debug

advanced

Why does the database not reset between tests despite using RefreshDatabase?

You have a Laravel test class using the RefreshDatabase trait, but data inserted in one test remains in the next test. What is the most likely cause?

A The migrations are not defined in the <code>database/migrations</code> folder.

B The <code>RefreshDatabase</code> trait is used inside a test method instead of the class.

C The database connection is set to an in-memory SQLite database.

D The test class extends <code>PHPUnitFrameworkTestCase</code> instead of <code>TestsTestCase</code>.

💡 Hint

Think about the base class that sets up Laravel's testing environment.

If the test class extends PHPUnitFrameworkTestCase directly, Laravel's testing features like database refreshing won't work because the Laravel application is not bootstrapped.

🧠 Conceptual

expert

Why might you choose RefreshDatabase over DatabaseTransactions in Laravel tests?

Both RefreshDatabase and DatabaseTransactions traits reset the database state between tests. What is a key reason to prefer RefreshDatabase in some cases?

A <code>DatabaseTransactions</code> cannot be used with any Laravel model factories.

B <code>RefreshDatabase</code> is faster because it uses transactions instead of migrations.

C <code>RefreshDatabase</code> runs migrations fresh, supporting tests that modify schema or use multiple database connections.

D <code>DatabaseTransactions</code> permanently deletes data, while <code>RefreshDatabase</code> only rolls back.

💡 Hint

Think about schema changes and database connection types.

RefreshDatabase runs migrations fresh before each test, which is necessary if your tests change the database schema or use multiple connections. DatabaseTransactions only rolls back data changes within a transaction and does not reset schema.