From 1a356168fbf1a270d99965d77f92b6950c5bd3c5 Mon Sep 17 00:00:00 2001 From: Amy Haywood Dutton Date: Mon, 19 Feb 2024 12:34:24 -0600 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Changes=20optimisation=20to=20Am?= =?UTF-8?q?erican=20English=20spelling?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/docs/testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/testing.md b/docs/docs/testing.md index ea0f30d55173..46304dbaa622 100644 --- a/docs/docs/testing.md +++ b/docs/docs/testing.md @@ -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.