From 766bc5cd77da94f1706e8f68d6264c2a6724516f Mon Sep 17 00:00:00 2001 From: Max Schmitt Date: Mon, 23 Oct 2023 18:22:17 +0200 Subject: [PATCH] docs: .NET ParallelScope (#27745) Fixes https://github.com/microsoft/playwright-dotnet/issues/2732 --- docs/src/test-runners-csharp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/test-runners-csharp.md b/docs/src/test-runners-csharp.md index 83d6bc58b0..bc34128c4f 100644 --- a/docs/src/test-runners-csharp.md +++ b/docs/src/test-runners-csharp.md @@ -110,7 +110,7 @@ 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 (`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. +Only `ParallelScope.Self` is 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.