Tom Longhurst

Hi @biqas - If you're executing using `dotnet run` then Console output should display normally. If you're using Visual Studio, I think they're still working on showing the Console output...

I don't quite understand what you mean by "logger output to test output"? Are you talking about the visual studio results window? If not, can you give an equivalent example...

@biqas You can do `Logger = new DefaultLogger()` for a logger that writes to the console. Otherwise you can define your own class that inherits from `TUnitLogger` and then define...

> I think the big thing that @biqas is after (and myself as well) is the ability to log and capture logs for a given test and provide that as...

Also it might be a limit or the ide. As this is all quite new there's multiple parts here that all need to work together. I think TUnit is fulfilling...

> These links below might provide some hints as to what @biqas is inquiring about. > > https://blog.martincostello.com/writing-logs-to-xunit-test-output/ > > and > > https://www.meziantou.net/how-to-view-logs-from-ilogger-in-xunitdotnet.htm I'll take a look but this...

> I really miss `ITestOutputHelper`, or an equivalent. I do lots of weird stuff through tests, like dumping initializer syntax of the data on a failing test, (using my lib...

As an update for everyone on test IDE output windows. The test metadata I send behind the scenes to the test framework has only recently included support for test output...

Jetbrains have marked the issue as fixed. Says it'll be available in the Next 2024.3 public build. 🤞

This is now working in 2024.3 EAP 4. You can either download that, or wait until the official 2024.3 release.