From f9de5eb826f080ef5ce8a33d6c63ca0fbc56461c Mon Sep 17 00:00:00 2001 From: Dan Moseley Date: Mon, 3 Jul 2023 20:54:05 -0500 Subject: [PATCH] Update testing.md --- docs/workflow/testing/libraries/testing.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/workflow/testing/libraries/testing.md b/docs/workflow/testing/libraries/testing.md index 1ebd87ac40715..7eeba3bc257e6 100644 --- a/docs/workflow/testing/libraries/testing.md +++ b/docs/workflow/testing/libraries/testing.md @@ -155,6 +155,24 @@ It is important to highlight that these tests do not use the standard XUnit test - `-nonamespace` - `-parallel` +### Speeding up inner loop + +A couple of flags that are sometimes helpful when iterating on a test project in the shell: + +- `/p:testnobuild=true` -- modifies `/t:test` so that it doesn't do a build before running the tests. Useful if you didn't change any code and you don't want to even check timestamps. +- `--no-restore` -- modifies `dotnet build` so that it doesn't attempt to restore packages. Useful if you're already up to date with NuGet packages. + +Together these can cut a couple seconds off when you're iterating. + +Putting these together, here's an example of running a single test method in a particular test project, with those flags applied: + +```cmd +# assuming we're in src\libraries\System.Text.RegularExpressions +dotnet build --no-restore /t:test /p:testnobuild=true /p:xunitoptions=" -method System.Text.RegularExpressions.Tests.RegexMatchTests.Match" tests\FunctionalTests +``` + +If you change code, you'd need to remove `/p:testnobuild=true` from the command above. + ### Viewing XUnit logs It's usually sufficient to see the test failure output in the console. There is also a test log file, which you can find in a location like `...\runtime\artifacts\bin\System.Text.RegularExpressions.Tests\Debug\net8.0\testResults.xml`. It can be helpful, for example, to grep through a series of failures, or to see how long a slow test actually took.