#Dagger vs Testcontainers
1 messages · Page 1 of 1 (latest)
🧵
I started a github discussion thread on this topic: https://github.com/dagger/dagger/discussions/11710
FYI @fresh dock @hearty hazel
Context Dagger is great at building and running integration test harnesses. This is done in two parts: Execution environment: the container that will run the test code Service dependencies: service...
Awsome Hype ! Keep up the good job 🚀
The closest aspect of e2e tests is this Doc. about CI, with the "hello-dagger-template" Vue/Vite project having one Cypress e2e test (which you have to fix with cy.contains('h1', 'Hello from Dagger!') to pass) : https://docs.dagger.io/getting-started/quickstarts/ci/
yeah to be clear, running e2e tests is a very common use of Dagger (probably the number one use case). It's orchestrating test dependencies from within the test code that is less common. Typically when orchestrating e2e tests in Dagger, you setup the whole test scaffolding (both execution environment + service dependencies) in one go, from outside the test code.