From 76a5c247b1419f78e2c5075630e21d3939e7ff15 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adri=C3=A0=20Marcet?= Date: Mon, 4 May 2026 13:33:13 +0200 Subject: [PATCH] Fix formatting issues in part5d.md --- src/content/5/en/part5d.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/5/en/part5d.md b/src/content/5/en/part5d.md index b26dbe6f305..c7df5af68d2 100644 --- a/src/content/5/en/part5d.md +++ b/src/content/5/en/part5d.md @@ -233,7 +233,7 @@ describe('Note app', () => { // highlight-line }) ``` -Before we move on, let's break the tests one more time. We notice that the execution of the tests is quite fast when they pass, but much slower if the they do not pass. The reason for this is that Playwright's policy is to wait for searched elements until [they are rendered and ready for action](https://playwright.dev/docs/actionability). If the element is not found, a _TimeoutError_ is raised and the test fails. Playwright waits for elements by default for 5 or 30 seconds [depending on the functions used in testing](https://playwright.dev/docs/test-timeouts#introduction). +Before we move on, let's break the tests one more time. We notice that the execution of the tests is quite fast when they pass, but much slower if they do not pass. The reason for this is that Playwright's policy is to wait for searched elements until [they are rendered and ready for action](https://playwright.dev/docs/actionability). If the element is not found, a _TimeoutError_ is raised and the test fails. Playwright waits for elements by default for 5 or 30 seconds [depending on the functions used in testing](https://playwright.dev/docs/test-timeouts#introduction). When developing tests, it may be wiser to reduce the waiting time to a few seconds. According to the [documentation](https://playwright.dev/docs/test-timeouts), this can be done by changing the file _playwright.config.js_ as follows: