testcontainers / testcontainers/testcontainers-java
Collaborate on domain language across testcontainers implementations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
On a meetup today I talked to @kiview who had been presenting testcontainers and mentioned the upcoming 2.0 refactor.
I suggest we take this opportunity to work out a language / implementation agnostic domain of behaviors for testcontainers so whatever implementation is used the API would be similar and easy to grasp.
This can also apply to conceptual problems like how to implement certain waiting strategies or how to integrate with docker-compose or Kubernetes.
I opened https://github.com/testcontainers/testcontainer-go/issues/21 to track this on the go implementation which I'd like to contribute to.
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
No files, tests, or entry points are identified. Start by reviewing the proposed language- and implementation-agnostic behavior model and the linked testcontainers-go issue 21. Done would require an agreed shared domain of behaviors across implementations, including waiting strategies and Docker Compose or Kubernetes integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, java, kubernetes
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100