Info logging should include a header with the test id

[AArnott]

I'm migrating some tests from xunit to TUnit. I've replaced use of the ITestOutputHelper in xunit with use of the TUnit logger. In logging information from tests, I get output like this:

I was surprised to see any output at all, since I'm logging Info which I expected would be hidden by default. But the real issue is that the logged messages aren't associated at the console with the test id, so these messages aren't nearly as useful. How can I get the console log to include the test name as a header before any messages that would be printed from a test?

I'm not wanting to see the name of every test... just the name of tests that log messages. Arranged such that I can see which test logged which messages.

[AArnott]

An a related note, I find that the only way I can prevent these logged messages from appearing in the console is to use LogTrace instead of LogInformation. But by so doing, it also hides the output from Test Explorer's "Test Detail Summary" panel, which is where I always go to see it.

Is there a way to get the messages to show up in Test Explorer, and be included in log files, without it appearing in the console log, all by default?

[AArnott]

I found https://tunit.dev/docs/customization-extensibility/logging which tells me I can modify my test running script to include --log-level Warning which gets the console cleaner while keeping the Info data in the Test Explorer pane. Thanks.

I would still love to be able to derive my own TUnitLogger that can collect messages and dump them all at once when a test is over, so that it can add a test name header above them. Is there any way to do that?

[thomhurst]

In the next version I'll give you a way to override GetMessage so you can format how you like

[AArnott]

Awesome. Can there also be a way to get a callback when a test is done so that I can dump all the messages to the console?

[thomhurst]

Should be able to use one on the test context like:

TestContext.Events.OnDispose += SomeDelegate

[AArnott]

Nice.

Ironically, just using Console.WriteLine in the test itself turned out to do exactly what I wanted. It's hidden from console logging by default and shows up in Test Explorer's test detail summary.