testcontainers-node
testcontainers-node copied to clipboard
Testcontainers is a NodeJS library that supports tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
Hi there! I was doing some testing with Testcontainers and LocalStack. I created a container as the docs say, but it turned out that when I stopped it, the lambda...
Hi 👋 I am experimenting with this project to use it as part of our test infrastructure with Playwright. So far, it's working well and has significantly helped us simplify...
When I was searching for it - I almost missed it, and found it by accident a moment before I gave up. I believe it's a too important feature to...
Encountering this issue when trying expose a host port in compose environment within jest global setup. **Expected Behaviour** **Description of the Issue** I am writing a series of tests and...
This PR is not a feature or bugfix, its only purpose serves to debug running tc-node in deno. Since this PR still uses npm libraries for calling out to docker,...
**Expected Behaviour** We want to replicate the profile we use for deploying a chromium container using https://github.com/Zenika/alpine-chrome We use the flag `--security-opt seccomp=$(pwd)/chrome.json` **Actual Behaviour** Cannot add this flag
When we do an exec, we get an { ouput, exitCode }. It would be nice if we could get a { stdout, stderr, exitCode }. Do you guys think...
**Expected Behaviour** We have a docker compose stack that we manage through testcontainers. Previous to v10.11.0, the stack came up normally. **Actual Behaviour** With v10.11.0, the stack fails to come...
Setting `COMPOSE_COMPATIBILITY` flag changes behavior of separators and break Compose v2 integration
**Expected Behaviour** The separators for docker container names when using docker compose should be uniform, either `_` or `-`. **Actual Behaviour** Currently, `testcontainers-node` has no way to set `--compatibility` on...
**Expected Behaviour** I would expect that test containers would log error when I use `withWaitStrategy` with not existing container name OR that the documentation highlights where should I serviceName vs...