From 4bf5b091d5b510eadc80f6f46449a409e8574892 Mon Sep 17 00:00:00 2001 From: Steven Boutcher Date: Fri, 25 Aug 2023 14:50:35 -0500 Subject: [PATCH] Fix run-on sentence in Best Practices docs (#26622) --- docs/src/best-practices-js.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/best-practices-js.md b/docs/src/best-practices-js.md index 53dc975443..b81e5a1e31 100644 --- a/docs/src/best-practices-js.md +++ b/docs/src/best-practices-js.md @@ -288,7 +288,7 @@ npx playwright test --shard=1/3 ### Use Soft assertions -If your test fails, Playwright will give you an error message showing what part of the test failed which you can see either in VS Code, the terminal, the HTML report, or the trace viewer. However, you can also use [soft assertions](/test-assertions.md#soft-assertions) these do not immediately terminate the test execution, but rather compile and display a list of failed assertions once the test ended. +If your test fails, Playwright will give you an error message showing what part of the test failed which you can see either in VS Code, the terminal, the HTML report, or the trace viewer. However, you can also use [soft assertions](/test-assertions.md#soft-assertions). These do not immediately terminate the test execution, but rather compile and display a list of failed assertions once the test ended. ```js // Make a few checks that will not stop the test when failed...