Very good thought about writing tests and generating the code! It would solve a lot of issues in the production code it self, like simplicity, readability, complexity and, of course, test coverage :)
It’s seems more a beginner guide than a mastering lecture. The example are pretty simple. I would suggest a deeper discussion about why use and harder use cases.
Hi Dmitry, here's the reply from Oleg (some issues with answering directly here): There is a small example in the docs about ElasticSearch (www.testcontainers.org/modules/elasticsearch/) and you can also take a look at the ElasticSearch module tests which can suggest some patterns of use: github.com/testcontainers/testcontainers-java/blob/main/modules/elasticsearch/src/test/java/org/testcontainers/elasticsearch/ElasticsearchContainerTest.java
We are facing issue with running TC in the cloud. In order to run tests in pipeline we need docker in docker. Which is a security threat. Any idea around it?
Hi Alex, here's the reply from Oleg (some issues regarding him being able to post reply directly) - You have full control of how you want to capture container logs (www.testcontainers.org/features/container_logs/), for example you can have a LogConsumer follow the logs and write them into a file, or use a ```Slf4jLogConsumer logConsumer = new Slf4jLogConsumer(LOGGER); container.followOutput(logConsumer);``` with a Slf4j logger that is configured to write everything into a file.
TestContainers is only good as the image you can use for testing. Like say oracle-xe, ...last time I check you can't create your own user to executed DDL but you need to use "test" user or something, which is pathetic.
please stop using spring and spring specific things in your demos. the world is changing. there is a new generation of framwworks outthere. in a spring conf go for it. but if you do a testcontainers demo try to keep it neutral thanks!
Don't discount the fact that knowledge of Spring and SpringBoot is nearly universal in the Java ecosystem and this makes the knowledge presented here immediately understandable/applicable to the majority. This, without preventing people who prefer a next-gen framework from learning things, knowing that you can skip the Spring/SpringBoot specific parts and focus on the rest.
Very good thought about writing tests and generating the code! It would solve a lot of issues in the production code it self, like simplicity, readability, complexity and, of course, test coverage :)
It’s seems more a beginner guide than a mastering lecture. The example are pretty simple. I would suggest a deeper discussion about why use and harder use cases.
This was brilliant! Thanks for sharing!
Thanks for such a great video. Would be nice to see an example of Elasticsearch 8 test-container which is not so trivial as Redis, Rabbit or Postgres
Hi Dmitry, here's the reply from Oleg (some issues with answering directly here): There is a small example in the docs about ElasticSearch (www.testcontainers.org/modules/elasticsearch/) and you can also take a look at the ElasticSearch module tests which can suggest some patterns of use: github.com/testcontainers/testcontainers-java/blob/main/modules/elasticsearch/src/test/java/org/testcontainers/elasticsearch/ElasticsearchContainerTest.java
Awesome really, where can i find that example?
We are facing issue with running TC in the cloud. In order to run tests in pipeline we need docker in docker. Which is a security threat. Any idea around it?
If you're deploying to k8s, you could use KubeDock as an alternative to DinD.
A little bit of an eccentric guy, but great presentation of a cool technology. Well done.
Can You please provide with the Gihub link?
Is there a reason why he created redis as a GenericContainer but Postgres and Kafka as PostgresContainer and KafkaContainer? Just curious.
Very cool 😎
🇨🇴🧔🏻👍🏼🤝🏼 Saludos desde Colombia.
how to redirect container logs into host file?
Hi Alex, here's the reply from Oleg (some issues regarding him being able to post reply directly) - You have full control of how you want to capture container logs (www.testcontainers.org/features/container_logs/), for example you can have a LogConsumer follow the logs and write them into a file, or use a
```Slf4jLogConsumer logConsumer = new Slf4jLogConsumer(LOGGER); container.followOutput(logConsumer);``` with a Slf4j logger that is configured to write everything into a file.
@@JavaWithMala thanks for response
You know this guy is a Java dev because it took his IDE 21 minutes to load.
This should be in russian, this is our programm, our container and our man.
TestContainers is only good as the image you can use for testing. Like say oracle-xe, ...last time I check you can't create your own user to executed DDL but you need to use "test" user or something, which is pathetic.
please stop using spring and spring specific things in your demos.
the world is changing. there is a new generation of framwworks outthere.
in a spring conf go for it. but if you do a testcontainers demo try to keep it neutral
thanks!
Don't discount the fact that knowledge of Spring and SpringBoot is nearly universal in the Java ecosystem and this makes the knowledge presented here immediately understandable/applicable to the majority.
This, without preventing people who prefer a next-gen framework from learning things, knowing that you can skip the Spring/SpringBoot specific parts and focus on the rest.
use Micronaut
imho, spring is totally fine here, theremore, spring is de facto default java framework
@@PlayGameToday this is what I mean as its one of the next gen frameworks.
but I think for this purpose its better to show testcontainer on pure java
lol majority of the enterprise uses spring as their go to frameworks for microservices. Seldom uses micronaut or quarkus.