unit tests are nice but integration tests are life saver, always have them on side
unit tests are nice but integration tests are life saver, always have them on side
I thought I wrote on my blog about how excited I'm to say hello to projects I don't feel like I am contributing enough anymore. I left as #CNCF ambassador, #docker captain, #testcontainer maintainer and after an amazing experience as #RelEng for #kubernetes a few years ago I decided it was not for me and yesterday I received this email ❤️ I know numbers are important, I know how complicated it is to manage communities where everyone matters and I am glad my spot is available for someone else now!
📖 Article: "Test Containers and Clean Architecture"
Key Highlights:
✅ Exploring Clean Architecture principles for robust software.
✅ A practical guide to leveraging Test Containers for testing.
✅ Real-world examples and case studies.
✅ The future of software development trends.
Read the full article here: https://dev.to/ticinoswcraft/tests-infrastructure-1gko
Hey Fediverse, the Couchbase #testcontainer is using 5 GB of my RAM. Is there a setting somewhere to reign in the memory consumption?
In meiner letzten Kolumne ging es um den neuen #testcontainer und #dockercompose Support von #SpringBoot 3.1. Viel Spaß beim lesen: https://www.innoq.com/de/articles/2023/09/spring-boot-testcontainers-and-docker-compose/
Lust auf #TestContainer? Am 6.10. veranstaltet dazu die @jugstuttgart einen Workshop. Weitere Infos unter https://www.jugs.org/veranstaltungen/testcontainers/
@SaturniusMons It’s more #TestContainer’s at the moment - I did manage to trace one issue down to me dropping an EXPOSE line in the DockerFile ( which didn’t break the app as its in compose’s yaml etc ) - but not getting https://gist.github.com/talios/b50892f78de546b3d783a6eae8870a82 - with TestContainers failing saying `nc: not found` (which doesn’t exist in my container, but never did), definitely something odd with networking.
@hovfefe @davidfowl We are trying a different approach to testing (treating the API as a black box and testing the outside only) so spent most of my time fighting the test framework. That said, the #testcontainer implementation itself was good other than having to do a StartAsync().Wait(); for each container in the constructor of the custom WebApplicationFactory, so I can get the mapped ports to use in ConfigureWebHost()
I'm sure my implementation is not optimal by a long way but it works.
[New Blog Post] Using Testcontainers in Spring Boot Tests combined with JUnit5 for Selenium Tests
https://blog.sandra-parsick.de/2022/11/21/using-testcontainers-selenium-in-spring-boot-tests/
@ben is there a "simpler" way for testing e.g. bots or custom apps locally? Maybe with #TestContainer ? @kiview @oli
I cannot help but love how naturally #ArrowKt composes with #kotlin, taking away so much complexity of learning to work with FP.
Composing two #TestContainer resources, in parallel. No wrappers, flatMap, or bind in sight! 😍 A slightly bigger, but more real-world example today.