diff --git a/docs/src/test-projects-js.md b/docs/src/test-projects-js.md index f0453e228e..fd551400c7 100644 --- a/docs/src/test-projects-js.md +++ b/docs/src/test-projects-js.md @@ -188,26 +188,26 @@ export default defineConfig({ When working with tests that have a dependency, the dependency will always run first and once all tests from this project have passed, then the other projects will run in parallel. Running order: -1. Tests in 'setup' project run +1. Tests in the 'setup' project run. Once all tests from this project have passed, then the tests from the dependent projects will start running. -2. Tests in 'chromium', 'webkit' and 'firefox' projects run in parallel +2. Tests in the 'chromium', 'webkit' and 'firefox' projects run together. By default, these projects will [run in parallel](./test-parallel.md), subject to the maximum workers limit. chromium, webkit and firefox projects depend on setup project If there are more than one dependency then these project dependencies will be run first and in parallel. If the tests from a dependency fails then the tests that rely on this project will not be run. Running order: -1. Tests in 'Browser Login' and 'DataBase' projects run in parallel +1. Tests in the 'Browser Login' and 'DataBase' projects run in parallel: - 'Browser Login' passes - ❌ 'DataBase' fails! -1. “e2e tests” is not run! +1. The 'e2e tests' project is not run! Browser login project is blue, database is red and e2e tests relies on both ### Teardown -You can also [`property: TestProject.teardown`] your setup by adding a teardown property to your setup project. This will run after all dependent projects have run. See the [teardown guide](./test-global-setup-teardown.md#teardown) for more information. +You can also teardown your setup by adding a [`property: TestProject.teardown`] property to your setup project. Teardown will run after all dependent projects have run. See the [teardown guide](./test-global-setup-teardown.md#teardown) for more information. global setup and teardown