From 6173014a7564caf53dc63fe2387530258bab642b Mon Sep 17 00:00:00 2001 From: Daniel Eisterhold Date: Mon, 22 May 2023 13:02:30 -0500 Subject: [PATCH] docs: fix link to MSTest section on test-runner page (#23200) Signed-off-by: Daniel Eisterhold --- docs/src/intro-csharp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/intro-csharp.md b/docs/src/intro-csharp.md index 2d4a0445a0..3df448756e 100644 --- a/docs/src/intro-csharp.md +++ b/docs/src/intro-csharp.md @@ -5,7 +5,7 @@ title: "Installation" Playwright was created specifically to accommodate the needs of end-to-end testing. Playwright supports all modern rendering engines including Chromium, WebKit, and Firefox. Test on Windows, Linux, and macOS, locally or on CI, headless or headed with native mobile emulation. -You can choose to use [NUnit base classes](./test-runners.md#nunit) or [MSTest base classes](./test-runners.md#nunit) that Playwright provides to write end-to-end tests. These classes support running tests on multiple browser engines, parallelizing tests, adjusting launch/context options and getting a [Page]/[BrowserContext] instance per test out of the box. Alternatively you can use the [library](./library.md) to manually write the testing infrastructure. +You can choose to use [NUnit base classes](./test-runners.md#nunit) or [MSTest base classes](./test-runners.md#mstest) that Playwright provides to write end-to-end tests. These classes support running tests on multiple browser engines, parallelizing tests, adjusting launch/context options and getting a [Page]/[BrowserContext] instance per test out of the box. Alternatively you can use the [library](./library.md) to manually write the testing infrastructure. 1. Start by creating a new project with `dotnet new`. This will create the `PlaywrightTests` directory which includes a `UnitTest1.cs` file: