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

docs: Within describeScenario documentation, change optimisation to use American English #10032

Merged
merged 1 commit into from
Feb 19, 2024
+1 −1
Merged

docs: Within describeScenario documentation, change optimisation to use American English #10032

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
2 changes: 1 addition & 1 deletion docs/docs/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1696,7 +1696,7 @@ Only the posts scenarios will be present in the database when running the `posts
During the run of any single test, there is only ever one scenario's worth of data present in the database: users.standard *or* users.incomplete.
### describeScenario - a performance optimisation
### describeScenario - a performance optimization
The scenario feature described above should be the base starting point for setting up test that depend on the database. The scenario sets up the database before each scenario _test_, runs the test, and then tears down (deletes) the database scenario. This ensures that each of your tests are isolated, and that they do not affect each other.
Expand Down
Loading