Summary

Establish proof-of-concept for testcontainer-based testing by wrapping drivers-evergreen-tools orchestration in testcontainers. This enables isolated, parallel test execution and cleaner test dependency management without polluting consumer dependency trees.

See GODRIVER-3721 for basis.

Motivation

Who is the affected end user?

Go Driver engineering team and downstream consumers concerned about CVEs in test-only dependencies.

How does this affect the end user?

Current shared orchestration creates bottlenecks in test execution time. Test-only dependencies (like testify) in the main module trigger confusing CVE reports for consumers who never use them.

How likely is it that this problem or use case will occur?

Main path - affects every test run locally and in CI.

If the problem does occur, what are the consequences and how severe are they?

Performance concern: slow test feedback loops impact developer productivity. Dependency concern: CVE noise confuses consumers.

Is this issue urgent?

Not urgent, but foundational for future test infrastructure improvements.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Test improvements only no functional impact on driver behavior.

Cast of Characters

Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders:

Channels & Docs

Slack Channel

[Scope Document|some.url]

[Technical Design Document|some.url]