From 54004d08bf7090411e1cf082a7dd88d636785367 Mon Sep 17 00:00:00 2001 From: "microsoft-playwright-automation[bot]" <203992400+microsoft-playwright-automation[bot]@users.noreply.github.com> Date: Tue, 24 Feb 2026 10:25:23 +0000 Subject: [PATCH] feat(roll): roll to ToT Playwright (24-02-26) --- dotnet/docs/trace-viewer.mdx | 2 +- java/docs/trace-viewer.mdx | 2 +- nodejs/docs/best-practices.mdx | 2 +- nodejs/docs/trace-viewer.mdx | 2 +- python/docs/trace-viewer.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/dotnet/docs/trace-viewer.mdx b/dotnet/docs/trace-viewer.mdx index 71c159fbb9..3ceb62a581 100644 --- a/dotnet/docs/trace-viewer.mdx +++ b/dotnet/docs/trace-viewer.mdx @@ -10,7 +10,7 @@ import LiteYouTube from '@site/src/components/LiteYouTube'; ## Introduction -Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-the-trace) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). +Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-trace-viewer) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). ## Opening Trace Viewer diff --git a/java/docs/trace-viewer.mdx b/java/docs/trace-viewer.mdx index bcb0b0fb7e..2bf2197014 100644 --- a/java/docs/trace-viewer.mdx +++ b/java/docs/trace-viewer.mdx @@ -10,7 +10,7 @@ import LiteYouTube from '@site/src/components/LiteYouTube'; ## Introduction -Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-the-trace) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). +Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-trace-viewer) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). ## Opening Trace Viewer diff --git a/nodejs/docs/best-practices.mdx b/nodejs/docs/best-practices.mdx index a4e158c45b..1b8e4e20c9 100644 --- a/nodejs/docs/best-practices.mdx +++ b/nodejs/docs/best-practices.mdx @@ -187,7 +187,7 @@ await expect(page.getByText('welcome')).toBeVisible(); #### Local debugging -For local debugging we recommend you [debug your tests live in VSCode.](/getting-started-vscode.mdx#live-debugging) by installing the [VS Code extension](./getting-started-vscode.mdx). You can run tests in debug mode by right clicking on the line next to the test you want to run which will open a browser window and pause at where the breakpoint is set. +For local debugging we recommend you [debug your tests live in VSCode.](./getting-started-vscode.mdx#debugging-your-tests) by installing the [VS Code extension](./getting-started-vscode.mdx). You can run tests in debug mode by right-clicking on the line next to the test you want to run which will open a browser window and pause at where the breakpoint is set. debugging tests in vscode diff --git a/nodejs/docs/trace-viewer.mdx b/nodejs/docs/trace-viewer.mdx index aeb98ff0f4..7f048ac17c 100644 --- a/nodejs/docs/trace-viewer.mdx +++ b/nodejs/docs/trace-viewer.mdx @@ -10,7 +10,7 @@ import LiteYouTube from '@site/src/components/LiteYouTube'; ## Introduction -Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-the-trace) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). +Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-trace-viewer) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). ###### diff --git a/python/docs/trace-viewer.mdx b/python/docs/trace-viewer.mdx index 66a527b1d5..2c49b94d2f 100644 --- a/python/docs/trace-viewer.mdx +++ b/python/docs/trace-viewer.mdx @@ -10,7 +10,7 @@ import LiteYouTube from '@site/src/components/LiteYouTube'; ## Introduction -Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-the-trace) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). +Playwright Trace Viewer is a GUI tool that helps you explore recorded Playwright traces after the script has run. Traces are a great way for debugging your tests when they fail on CI. You can open traces [locally](#opening-trace-viewer) or in your browser on [trace.playwright.dev](https://trace.playwright.dev). ## Opening Trace Viewer