The seed is printed in the headers when diagnostic messages are enabled.

When using dotnet run, there is one variable which influences how easy it is to see the seed.

• For native xUnit.net UX, it just shows up:

  

• For Microsoft Testing Platform UX, you need to pass --xunit-info to see the xUnit.net messages:

  

When using dotnet test, there are several variables which can influence how easy it is to see the seed.

• For VSTest mode, with .NET SDK 9 and using Windows Terminal, it should just show up:

  

• For VSTest mode, with .NET SDK 8 or older (or if you're not using Windows Terminal), it will only show up if you enable normal verbosity with the console logger with --logger "console;verbosity=normal":

  

• For Microsoft Testing Platform mode, you need to pass all of -tl:off -p:TestingPlatformCaptureOutput=false -- --xunit-info so that the xUnit.net headers will be printed:

  

  The -tl:off switch turns of Windows Terminal mode (which is required, because the new Windows Terminal mode always hides the output). The -p:TestingPlatformCaptureOutput=false switch tells dotnet test to log to the console in addition to logging to the log file in the TestResults folder.