modelcontextprotocol / modelcontextprotocol/registry
Use `testcontainers` for integration tests
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Currently, Makefile has targets to run Postgres which is then used in integartion tests.
It might be better to use testcontainers (example here), which has the advantage of allowing entirely isolated tests that can be executed in parallel and reduces dependency on the toolchain, simplifying automation.
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 with the Postgres targets in Makefile and the existing integration tests, then compare their setup with the linked Go testcontainers Postgres usage example. The change is complete when the integration tests provision isolated Postgres containers, can run in parallel, and no longer depend on the Makefile-managed Postgres toolchain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgres
- Domain
- databases, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100