I tried these failing tests locally, They work in all python versions (used venv) but were flaky and I had to try multiple time.
mssql test didnt work locally too.

@tillahoffmann Can you please review this change?

@tillahoffmann Thanks for the review comments. I have accommodated those in latest commit.

assert consumer.end_offsets([tp])[tp] == 1, "Expected exactly one test message to be present on test topic !"

This is going to ensure that we will have one and only one message in the consumer in integration test.

assert consumer.end_offsets([tp])[tp] == 1, "Expected exactly one test message to be present on test topic !"

This is going to ensure that we will have one and only one message in the consumer in integration test.

I understand. Then it looks like the for loop and the assertion within don't add confidence to the test. Would you consider to scrap them?

@ash1425 Hey Ashay, do you have bandwidth working on the PR? If not, maybe I can help to cross the finish line?

@YikSanChan
Thanks for offering to help. I have invited you as collaborator to my fork.

For now, I have incorporated all the review comments and merged upstream changes to resolve the conflicts. I think we should be good to approve and merge if all tests pass.

@ash1425 Great thanks! If there is any more comment from testcontainers members, I can try to resolve

@tillahoffmann Could you please taking a look? This is the feature I am looking for. Thank you!

@tillahoffmann CI seems happy. Are we good to get these changes in?