capture stdout

[Geal]

there's probably a way to get what's written on stdout in the sozu container, but also in the client and backend containers. This output should be displayed in case the test fails

[NotBad4U]

We can use a ToStringConsumer provide by testcontainers: https://www.testcontainers.org/usage/options.html#following-container-output

[NotBad4U]

WIP in branch follow-ouput-container

[Geal]

can we get the output from the other containers as well?
Side question: since the node backend and sozu containers are reused for every test, how can we get the log messages specific to each test? For sozu we might be able to filter on the app id, but not for all of its log messages.

[NotBad4U]

can we get the output from the other containers as well?

Yes with same method

Side question: since the node backend and sozu containers are reused for every test

I was wrong about how @Rule work. A fresh container is spawn between each @Test.
So you'll get only the log message for your test which is what we want.

I did this here.
So follow-ouput-container is no longer useful anymore. I think we can close this issue now we know how to do it.

[Geal]

can you add output capture to all tests?

[NotBad4U]

Maybe we can try a trick with @BeforeEach where we create the Consumer and @AfterEach where we print the logs.

[NotBad4U]

Done in #26

[Geal]

reopening it because it's missing some code