Lags information to show how useful this package is

[khteh]

Please show where to look out for the output of the logs configured using this package. For example, in a VS2022 Output window, there is only "Tests" in the dropdown box which is relevant to a test run. And I only see the following:

This package is only useful in troubleshooting a running test using log printouts. Debug is not useful as we could set breakpoints and check the states of the tests. Right now, what I experience is that my tests could run further in Debug session compared to running it and therefore, need the help of logging output to troubleshoot..

[martincostello]

I can add something to the docs, but this isn't something specific to this library.

This library outputs to the xunit output - where that appears is up to xunit itself based on how you use it.

For example, if the package is integrated correctly into a project you get output like this in Visual Studio 2022:

[khteh]

That's the problem. I don't see what you see - the "Standard Output" - in the tests window.

[martincostello]

Then there's something wrong with your test setup (or its failing too early for .NET to be able to log anything).

[khteh]

Does this package work with Serilog?

[martincostello]

Does this package work with Serilog?

This question is explicitly answered in the README. Please take a look.

[khteh]

Not really. Serilog.Sinks.XUnit packages uses the XUnit v2 while mine is using v3.

[martincostello]

It says it only works with the Microsoft implementation, therefore all others are not supported. Serilog is called out as an example. If they don't support v3 yet, then ask them when they're adding support.