vstest-docs VS awesome-dotnet

Environment variables is probably easiest, but vstest and dotnet test support your use case via runsettings arguments - more info here: https://github.com/microsoft/vstest-docs/blob/main/docs/RunSettingsArguments.md

I've had success creating my own logger by following this guide on the vsdocs github. Nowadays you don't have to deploy the assemblies for the custom logger to the vs install folders. vstest will scan the build output directory for assemblies that match the specified pattern, *.testlogger.dll. You can also specify the path for custom test adapters either from the command line or a runsettings file using the TestAdapterPath option (this is only available since v15.1 but you mentioned you've tried the html logger and I think that's much newer than v15.1). If you get stuck with the implementation you can try referring to vstest's own loggers: htmllogger, trxlogger.

Also something that may be relevant is that newer versions of the vstest platform allow you to override runsettings options when running tests from the command line, as described here.

vstest (c#) (I like this one a lot, architecture is very well documented here: https://github.com/Microsoft/vstest-docs)

Github .Net, Node, Cloud, React ... Awesomes

When checking for .NET related tools I tend to look at awewsome-dotnet and I couldn't find EfSchemaCompare or any other tool which seems to be related. Might be worth adding it there.

You can find interesting packages/projects for searching "awesome dotnet" in github. For example: https://github.com/quozd/awesome-dotnet https://github.com/thangchung/awesome-dotnet-core

Probably you might find some inspiration here - https://github.com/quozd/awesome-dotnet

Have you looked through https://github.com/quozd/awesome-dotnet/blob/master/README.md