Database testing (RefreshDatabase) in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the RefreshDatabase trait in Laravel testing?

The RefreshDatabase trait resets the database before each test by running migrations. This ensures tests start with a clean database state, avoiding data conflicts.

intermediate

How does RefreshDatabase differ from DatabaseTransactions in Laravel tests?

RefreshDatabase rebuilds the database schema before each test, while DatabaseTransactions wraps tests in a transaction that rolls back after the test. RefreshDatabase is better for tests that modify schema or need a fresh start.

beginner

When should you use RefreshDatabase in your Laravel tests?

Use RefreshDatabase when your tests change the database schema or when you want to ensure no leftover data affects your tests. It is ideal for integration tests involving database state.

intermediate

What happens behind the scenes when you use RefreshDatabase in a Laravel test?

Laravel runs the database migrations to rebuild the schema from scratch before each test. This wipes all data and resets tables to their initial state.

intermediate

Can RefreshDatabase be used with in-memory SQLite databases? Why or why not?

Yes, RefreshDatabase works well with in-memory SQLite databases because migrations run quickly and the database is fresh for each test run, making tests fast and isolated.

What does the RefreshDatabase trait do in Laravel tests?

A Caches database queries for faster tests

B Rolls back database transactions after each test

C Resets the database by running migrations before each test

D Seeds the database with test data automatically

RefreshDatabase resets the database by running migrations before each test to ensure a clean state.

Which trait is better for tests that only need to rollback data changes without rebuilding schema?

A WithFaker

B RefreshDatabase

C WithoutMiddleware

D DatabaseTransactions

DatabaseTransactions wraps tests in a transaction and rolls back changes, which is faster if schema changes are not needed.

Why might RefreshDatabase slow down tests compared to DatabaseTransactions?

A Because it runs migrations before each test

B Because it caches queries

C Because it disables middleware

D Because it seeds the database multiple times

Running migrations before each test takes more time than rolling back transactions.

Can RefreshDatabase be used with an in-memory SQLite database?

A Yes, it works well and is fast

B No, it only works with MySQL

C No, it requires a persistent database

D Yes, but it disables migrations

In-memory SQLite databases are fast and reset on each test, making RefreshDatabase ideal.

What is a key benefit of using RefreshDatabase in tests?

A Disables authentication middleware

B Ensures tests run with a clean database state

C Automatically mocks external APIs

D Improves query performance caching

It ensures each test starts with a fresh database, avoiding data conflicts.

Explain how the RefreshDatabase trait helps maintain test reliability in Laravel.

Think about how tests can fail if old data remains.

Compare RefreshDatabase and DatabaseTransactions traits and when to use each.

Consider schema changes versus data changes.