testcontainers / testcontainers/testcontainers-python
Feature: dependsOn functionality for DockerContainer
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 386
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
Description
What are you trying to do?
Improve TC-python feature parity with TC-java by enabling container to specify dependsOn, which should work similar to how depends_on in docker-compose does - container B that depends on container A won't be started until container A is in running state.
Why should it be done this way?
Control order/behavior for container startup in multi-container scenarios.
Other references:
Include any other relevant reading material about the enhancement.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating DockerContainer in TC-python and comparing its API with the TC-java dependsOn functionality and docker-compose startup behavior. Find the existing multi-container tests, then add coverage showing that container B does not start until container A reaches the running state; done means the behavior works for multi-container scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100