diff --git a/docs/src/release-notes-python.md b/docs/src/release-notes-python.md
index a4fe3882ed..4ce70e9811 100644
--- a/docs/src/release-notes-python.md
+++ b/docs/src/release-notes-python.md
@@ -4,6 +4,25 @@ title: "Release notes"
toc_max_heading_level: 2
---
+## Version 1.25
+
+### Announcements
+
+* 🎁 We now ship Ubuntu 22.04 Jammy Jellyfish docker image: `mcr.microsoft.com/playwright/python:v1.25.0-jammy`.
+* 🪦 This is the last release with macOS 10.15 support (deprecated as of 1.21).
+* ⚠️ Ubuntu 18 is now deprecated and will not be supported as of Dec 2022.
+
+### Browser Versions
+
+* Chromium 105.0.5195.19
+* Mozilla Firefox 103.0
+* WebKit 16.0
+
+This version was also tested against the following stable channels:
+
+* Google Chrome 104
+* Microsoft Edge 104
+
## Version 1.24
diff --git a/docs/src/running-tests-csharp.md b/docs/src/running-tests-csharp.md
index a76ece265e..b5129b2042 100644
--- a/docs/src/running-tests-csharp.md
+++ b/docs/src/running-tests-csharp.md
@@ -31,23 +31,13 @@ You can run a single test, a set of tests or all tests. Tests can be run on diff
- Running Tests on specific browsers
- ```bash tab=bash-bash
- BROWSER=webkit dotnet test
- ```
-
- ```batch tab=bash-batch
- set BROWSER=webkit
- dotnet test
- ```
-
- ```powershell tab=bash-powershell
- $env:BROWSER="webkit"
- dotnet test
+ ```bash
+ dotnet test -- Playwright.BrowserName=webkit
```
- Running Tests on multiple browsers
- To run your test on multiple browsers or configurations you need to invoke the `dotnet test` command multiple times. There you can then either specify the `BROWSER` environment variable (like the previous) or pass the `browser` via the runsettings file:
+ To run your test on multiple browsers or configurations you need to invoke the `dotnet test` command multiple times. There you can then either specify the `BROWSER` environment variable or set the `Playwright.BrowserName` via the runsettings file:
```bash
dotnet test --settings:chromium.runsettings
@@ -58,10 +48,9 @@ You can run a single test, a set of tests or all tests. Tests can be run on diff
```xml
-
-
-
-
+
+ chromium
+
```
diff --git a/docs/src/test-runners-csharp.md b/docs/src/test-runners-csharp.md
index c967c0b82c..b05cbfa21b 100644
--- a/docs/src/test-runners-csharp.md
+++ b/docs/src/test-runners-csharp.md
@@ -24,11 +24,13 @@ Playwright provides base classes to write tests with NUnit via the [`Microsoft.P
# Create a new project
dotnet new nunit -n PlaywrightTests
cd PlaywrightTests
+
# Add the required reference
dotnet add package Microsoft.Playwright.NUnit
dotnet build
+
# Install the required browsers and operating system dependencies
-pwsh bin\Debug\netX\playwright.ps1 install --with-deps
+pwsh bin/Debug/netX/playwright.ps1 install --with-deps
```
Modify the UnitTest1.cs:
@@ -104,7 +106,8 @@ dotnet test --filter "Name~Slogan"
### Running NUnit tests in Parallel
-By default NUnit will run all test files in parallel, while running tests inside each file sequentially. It will create as many processes as there are cores on the host system. You can adjust this behavior using the NUnit.NumberOfTestWorkers parameter.
+By default NUnit will run all test files in parallel, while running tests inside each file sequentially (`ParallelScope.Self`). It will create as many processes as there are cores on the host system. You can adjust this behavior using the NUnit.NumberOfTestWorkers parameter.
+Running test in parallel using `ParallelScope.All` or `ParallelScope.Fixtures` is not supported.
For CPU-bound tests, we recommend using as many workers as there are cores on your system, divided by 2. For IO-bound tests you can use as many workers as you have cores.
@@ -151,24 +154,18 @@ CLI. See the following example:
```xml
-
-
-
-
-
+
+ chromium
+
+ false
+ msedge
+
+
```
-```bash tab=bash-bash
-dotnet test -- TestRunParameters.Parameter\(name=\"browser\", value=\"chromium\"\) TestRunParameters.Parameter\(name=\"headless\", value=\"false\"\) TestRunParameters.Parameter\(name=\"channel\", value=\"msedge\"\)
-```
-
-```batch tab=bash-batch
-dotnet test -- TestRunParameters.Parameter(name=\"browser\", value=\"chromium\") TestRunParameters.Parameter(name=\"headless\", value=\"false\") TestRunParameters.Parameter(name=\"channel\", value=\"msedge\")
-```
-
-```powershell tab=bash-powershell
-dotnet test -- TestRunParameters.Parameter(name=\"browser\", value=\"chromium\") TestRunParameters.Parameter(name=\"headless\", value=\"false\") TestRunParameters.Parameter(name=\"channel\", value=\"msedge\")
+```bash
+dotnet test -- Playwright.BrowserName=chromium Playwright.LaunchOptions.Headless=false Playwright.LaunchOptions.Channel=msedge
```
### Using Verbose API Logs
@@ -177,29 +174,33 @@ When you have enabled the [verbose API log](./debug.md#verbose-api-logs), via th
### Using the .runsettings file
-When running tests from Visual Studio, you can take advantage of the `.runsettings` file.
+When running tests from Visual Studio, you can take advantage of the `.runsettings` file. The following shows a reference of the supported values.
-For example, to specify the amount of workers (`NUnit.NumberOfTestWorkers`), you can use the following snippet:
+For example, to specify the amount of workers you can use `NUnit.NumberOfTestWorkers` or to enable `DEBUG` logs `RunConfiguration.EnvironmentVariables`.
```xml
+
24
-
-```
-
-If you want to enable debugging, you can set the `DEBUG` variable to `pw:api` as documented, by doing:
-
-```xml
-
-
+
+
pw:api
+
+
+ chromium
+ 5000
+
+ false
+ msedge
+
+
```
@@ -224,11 +225,13 @@ Playwright provides base classes to write tests with MSTest via the [`Microsoft.
# Create a new project
dotnet new mstest -n PlaywrightTests
cd PlaywrightTests
+
# Add the required reference
dotnet add package Microsoft.Playwright.MSTest
dotnet build
+
# Install the required browsers and operating system dependencies
-pwsh bin\Debug\netX\playwright.ps1 install --with-deps
+pwsh bin/Debug/netX/playwright.ps1 install --with-deps
```
Modify the UnitTest1.cs:
@@ -304,7 +307,8 @@ dotnet test --filter "Name~Slogan"
### Running MSTest tests in Parallel
-By default MSTest will run all classes in parallel, while running tests inside each class sequentially. It will create as many processes as there are cores on the host system. You can adjust this behavior by using the following CLI parameter or using a `.runsettings` file, see below.
+By default MSTest will run all classes in parallel, while running tests inside each class sequentially (`ExecutionScope.ClassLevel`). It will create as many processes as there are cores on the host system. You can adjust this behavior by using the following CLI parameter or using a `.runsettings` file, see below.
+Running tests in parallel at the method level (`ExecutionScope.MethodLevel`) is not supported.
```bash
dotnet test --settings:.runsettings -- MSTest.Parallelize.Workers=4
@@ -357,24 +361,18 @@ CLI. See the following example:
```xml
-
-
-
-
-
+
+ chromium
+
+ false
+ msedge
+
+
```
-```bash tab=bash-bash
-dotnet test -- TestRunParameters.Parameter\(name=\"browser\", value=\"chromium\"\) TestRunParameters.Parameter\(name=\"headless\", value=\"false\"\) TestRunParameters.Parameter\(name=\"channel\", value=\"msedge\"\)
-```
-
-```batch tab=bash-batch
-dotnet test -- TestRunParameters.Parameter(name=\"browser\", value=\"chromium\") TestRunParameters.Parameter(name=\"headless\", value=\"false\") TestRunParameters.Parameter(name=\"channel\", value=\"msedge\")
-```
-
-```powershell tab=bash-powershell
-dotnet test -- TestRunParameters.Parameter(name=\"browser\", value=\"chromium\") TestRunParameters.Parameter(name=\"headless\", value=\"false\") TestRunParameters.Parameter(name=\"channel\", value=\"msedge\")
+```bash
+dotnet test -- Playwright.BrowserName=chromium Playwright.LaunchOptions.Headless=false Playwright.LaunchOptions.Channel=msedge
```
### Using Verbose API Logs
@@ -383,32 +381,35 @@ When you have enabled the [verbose API log](./debug.md#verbose-api-logs), via th
### Using the .runsettings file
-When running tests from Visual Studio, you can take advantage of the `.runsettings` file.
+When running tests from Visual Studio, you can take advantage of the `.runsettings` file. The following shows a reference of the supported values.
-For example, to specify the amount of workers (`MSTest.Parallelize.Workers`), you can use the following snippet:
+For example, to specify the number of workers, you can use `MSTest.Parallelize.Workers`. You can also enable `DEBUG` logs using `RunConfiguration.EnvironmentVariables`.
```xml
-
+
4
ClassLevel
-
-```
-
-If you want to enable debugging, you can set the `DEBUG` variable to `pw:api` as documented, by doing:
-
-```xml
-
-
+
+
pw:api
+
+
+ chromium
+ 5000
+
+ false
+ msedge
+
+
```
diff --git a/docs/src/trace-viewer-intro-csharp-java-python.md b/docs/src/trace-viewer-intro-csharp-java-python.md
index 409a565083..8fba36f8f9 100644
--- a/docs/src/trace-viewer-intro-csharp-java-python.md
+++ b/docs/src/trace-viewer-intro-csharp-java-python.md
@@ -101,7 +101,7 @@ playwright show-trace trace.zip
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 show-trace trace.zip
+pwsh bin/Debug/netX/playwright.ps1 show-trace trace.zip
```
diff --git a/docs/src/trace-viewer.md b/docs/src/trace-viewer.md
index 0f3bc3f270..4afe692df7 100644
--- a/docs/src/trace-viewer.md
+++ b/docs/src/trace-viewer.md
@@ -153,7 +153,7 @@ playwright show-trace trace.zip
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 show-trace trace.zip
+pwsh bin/Debug/netX/playwright.ps1 show-trace trace.zip
```
## Actions
@@ -220,7 +220,7 @@ playwright show-trace https://example.com/trace.zip
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 show-trace https://example.com/trace.zip
+pwsh bin/Debug/netX/playwright.ps1 show-trace https://example.com/trace.zip
```
## Using [trace.playwright.dev](https://trace.playwright.dev)
diff --git a/packages/playwright-core/src/cli/cli.ts b/packages/playwright-core/src/cli/cli.ts
index fe9bbca945..6b138d63ee 100755
--- a/packages/playwright-core/src/cli/cli.ts
+++ b/packages/playwright-core/src/cli/cli.ts
@@ -715,7 +715,7 @@ function buildBasePlaywrightCLICommand(cliTargetLang: string | undefined): strin
case 'java':
return `mvn exec:java -e -Dexec.mainClass=com.microsoft.playwright.CLI -Dexec.args="...options.."`;
case 'csharp':
- return `pwsh bin\\Debug\\netX\\playwright.ps1`;
+ return `pwsh bin/Debug/netX/playwright.ps1`;
default:
return `npx playwright`;
}
diff --git a/packages/playwright-core/src/server/registry/index.ts b/packages/playwright-core/src/server/registry/index.ts
index 2dd7922ecb..cdc6de680d 100644
--- a/packages/playwright-core/src/server/registry/index.ts
+++ b/packages/playwright-core/src/server/registry/index.ts
@@ -853,7 +853,7 @@ export function buildPlaywrightCLICommand(sdkLanguage: string, parameters: strin
case 'java':
return `mvn exec:java -e -Dexec.mainClass=com.microsoft.playwright.CLI -Dexec.args="${parameters}"`;
case 'csharp':
- return `pwsh bin\\Debug\\netX\\playwright.ps1 ${parameters}`;
+ return `pwsh bin/Debug/netX/playwright.ps1 ${parameters}`;
default:
return `npx playwright ${parameters}`;
}
@@ -92,7 +92,7 @@ playwright codegen --color-scheme=dark playwright.dev
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 codegen --color-scheme=dark playwright.dev
+pwsh bin/Debug/netX/playwright.ps1 codegen --color-scheme=dark playwright.dev
```
@@ -114,7 +114,7 @@ playwright codegen --timezone="Europe/Rome" --geolocation="41.890221,12.492348"
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 codegen --timezone="Europe/Rome" --geolocation="41.890221,12.492348" --lang="it-IT" maps.google.com
+pwsh bin/Debug/netX/playwright.ps1 codegen --timezone="Europe/Rome" --geolocation="41.890221,12.492348" --lang="it-IT" maps.google.com
```
@@ -138,7 +138,7 @@ playwright codegen --save-storage=auth.json
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 codegen --save-storage=auth.json
+pwsh bin/Debug/netX/playwright.ps1 codegen --save-storage=auth.json
```
@@ -158,7 +158,7 @@ playwright codegen --load-storage=auth.json github.com/microsoft/playwright
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 codegen --load-storage=auth.json github.com/microsoft/playwright
+pwsh bin/Debug/netX/playwright.ps1 codegen --load-storage=auth.json github.com/microsoft/playwright
```
@@ -178,7 +178,7 @@ playwright open --load-storage=auth.json github.com/microsoft/playwright
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 open --load-storage=auth.json github.com/microsoft/playwright
+pwsh bin/Debug/netX/playwright.ps1 open --load-storage=auth.json github.com/microsoft/playwright
```
diff --git a/docs/src/debug.md b/docs/src/debug.md
index daaec2ab09..970fc2b23b 100644
--- a/docs/src/debug.md
+++ b/docs/src/debug.md
@@ -193,7 +193,7 @@ playwright codegen wikipedia.org
```
```bash csharp
-pwsh bin\Debug\netX\playwright.ps1 codegen wikipedia.org
+pwsh bin/Debug/netX/playwright.ps1 codegen wikipedia.org
```
### Stepping through the Playwright script
diff --git a/docs/src/intro-csharp.md b/docs/src/intro-csharp.md
index bc0258cfe4..6f5aeb6a44 100644
--- a/docs/src/intro-csharp.md
+++ b/docs/src/intro-csharp.md
@@ -70,9 +70,11 @@ dotnet build
4. Install required browsers by replacing `netX` with the actual output folder name, e.g. `net6.0`:
```bash
-pwsh bin\Debug\netX\playwright.ps1 install
+pwsh bin/Debug/netX/playwright.ps1 install
```
+If `pwsh` is not available, you have to [install PowerShell](https://docs.microsoft.com/powershell/scripting/install/installing-powershell).
+
## Add Example Tests
Edit the `UnitTest1.cs` file with the code below to create an example end-to-end test:
diff --git a/docs/src/library-csharp.md b/docs/src/library-csharp.md
index f0ddc9d0ae..e0f737c492 100644
--- a/docs/src/library-csharp.md
+++ b/docs/src/library-csharp.md
@@ -19,7 +19,7 @@ dotnet add package Microsoft.Playwright
# Build the project
dotnet build
# Install required browsers - replace netX with actual output folder name, e.g. net6.0.
-pwsh bin\Debug\netX\playwright.ps1 install
+pwsh bin/Debug/netX/playwright.ps1 install
# If the pwsh command does not work (throws TypeNotFound), make sure to use an up-to-date version of PowerShell.
dotnet tool update --global PowerShell
diff --git a/docs/src/mock-js.md b/docs/src/mock-js.md
index a7e1c626c6..ce8726ad3f 100644
--- a/docs/src/mock-js.md
+++ b/docs/src/mock-js.md
@@ -5,7 +5,7 @@ title: "Mock APIs"
Playwright provides native support for most of the browser features. However, there are some experimental APIs
and APIs which are not (yet) fully supported by all browsers. Playwright usually doesn't provide dedicated
-atomation APIs in such cases. You can use mocks to test behavior of your application in such cases. This guide
+automation APIs in such cases. You can use mocks to test behavior of your application in such cases. This guide
gives a few examples.
diff --git a/docs/src/network.md b/docs/src/network.md
index d4bde2508a..4fea6546c8 100644
--- a/docs/src/network.md
+++ b/docs/src/network.md
@@ -719,7 +719,7 @@ playwright open --save-har=example.har --save-har-glob="**/api/**" https://examp
```bash csharp
# Save API requests from example.com as "example.har" archive.
-pwsh bin\Debug\netX\playwright.ps1 open --save-har=example.har --save-har-glob="**/api/**" https://example.com
+pwsh bin/Debug/netX/playwright.ps1 open --save-har=example.har --save-har-glob="**/api/**" https://example.com
```
### Recording HAR with a script
diff --git a/docs/src/release-notes-csharp.md b/docs/src/release-notes-csharp.md
index 95743663d4..0380ab4cfa 100644
--- a/docs/src/release-notes-csharp.md
+++ b/docs/src/release-notes-csharp.md
@@ -4,6 +4,52 @@ title: "Release notes"
toc_max_heading_level: 2
---
+## Version 1.25
+
+### New .runsettings file support
+
+`Microsoft.Playwright.NUnit` and `Microsoft.Playwright.MSTest` will now consider the `.runsettings` file and passed settings via the CLI when running end-to-end tests. See in the [documentation](https://playwright.dev/dotnet/docs/test-runners) for a full list of supported settings.
+
+The following does now work:
+
+```xml
+
+