Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[8.x] Adds documentation for LazilyRefreshDatabase #7325

Closed
wants to merge 1 commit into from
Closed

[8.x] Adds documentation for LazilyRefreshDatabase #7325

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions database-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,12 @@ Before proceeding much further, let's discuss how to reset your database after e
}
}

If you don't want to include the `Illuminate\Foundation\Testing\RefreshDatabase` on each test class that requires database access, you may
instead include the `Illuminate\Foundation\Testing\LazilyRefreshDatabase` trait on your abstract `Tests\TestCase`. This trait listens for calls
to the database within your tests and prepares the database for you as and when required.

> {tip} You should never use `Illuminate\Foundation\Testing\RefreshDatabase` and `Illuminate\Foundation\Testing\LazilyRefreshDatabase` together, as doing so will cause errors.

<a name="defining-model-factories"></a>
## Defining Model Factories

Expand Down