gdziadkiewicz commented on PR #204: URL: https://github.com/apache/logging-log4net/pull/204#issuecomment-2468412716
> > > @gdziadkiewicz can you test how just using "dotnet test" as a single step would look like? @fluffynuts do you have an idea why the windows output is much longer? (the macos and linux output are missing important inforamtion) > > > > > > Will do. > > the windows output looks like the output from `npm test` where the other two look like the output from `dotnet test` - the default verbosity on `dotnet test` will only dump out failing tests. > > I'd like to suggest that you install the Quackers test logger (https://www.nuget.org/packages/quackers.testlogger) - in conjunction with `zarro`, you'll get easier-to-read output (colored, with pass/fail icons) and it will suppress duplicate logging from the dotnet logger. This mechanism also allows for faster testing by running test assemblies in parallel, if log4net is ever looking at having a second tests assembly (or looking to reduce overall test-time: split existing tests across multiple test assemblies, as long as they all have a name ending in `.Tests`. Parallel testing is a fairly large reason why I use this approach everywhere. > > Alternatively, if y'all really want to eschew `npm test`, I suggest raising the verbosity for `dotnet test` - but I still heartily recommend the `zarro` / `quackers` route (both are written by me, and are our defaults at work) as you'll get the best output that way (eg: see https://github.com/fluffynuts/NExpect/actions/runs/11629746737/job/32387287891 for an example) WIP -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
