Get information about the Testcontainers environment

[HofmeisterAn]

Is your feature request related to a problem? Please describe.
In case of questions or bugs, information about the development environment (e.g. the Docker or Testcontainers version) are sometimes missing. Those information will help a lot to understand or categorize the issue.

Describe the solution you'd like

• Show a warning if no logger implementation is provided.
• Before Testcontainers creates any resources, it should output information about its state and environment.
• Add access to Docker Engine (server) information

Describe alternatives you've considered
-

Additional context
-

[kiview]

The first 2 seem more important, for the 3rd point, it depends if there are actual use cases for it.

[HofmeisterAn]

Ok, this is now the time all other languages make fun of .NET 😅. Yesterday I remembered again, logging to console from .NET tests is not that easy, especially not for us. We are in between of many test frameworks and applications. As far as I know, this is a limitation of the VSTest runner, you cannot simply write to console and expect an output (microsoft/vstest#799) 🤡.

Writing something to console goes usually through the test framework (xUnit.net has ITestOutputHelper, NUnit has TestContext, etc.). This is not a problem if you write tests for yourself, you just use whatever the test framework provides - but we cannot do that.

We need to ensure that our information is written in many different combinations:

• Via CLI (dotnet test)
• Via IDE (different output windows)
• Different test frameworks

I am not 100% sure why the current configuration partialy works with Serilog. E.g. we get an output in the pipeline (Ubuntu and Windows), in the IDE (Rider), but not on console (local). This is probably due to the Test Adapter, but at least in the pipeline and console it should be the same.

How can we add the feature?

• Write our own implementation of ITestLogger, ITestLoggerWithParameters.
• Write our own Test Adapter (I made a PoC, it works but I am not happy with it).
• Write to a file if the dev does not provide its own configuration (might be difficult to provide in some cases).
• Understand why Serilog partialy works.

The above suggestions need to ensure, that they work well with the test framework solution. E.g. my Test Adapter PoC messed up the output (indention, different prefix, etc.)