Use Docker containers for local testing

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Component/s: Containerized Testing
    • None
    • Use Docker containers for local testing
    • None
    • Hide

      Summary of necessary driver changes

      •  

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      •  

      Context for other referenced/linked tickets

      •  
      Show
      Summary of necessary driver changes   Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed)   Context for other referenced/linked tickets  
    • To Do
    • None
    • 0
    • 0
    • 0
    • 100
    • None
    • None
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      What is the problem or use case, what are we trying to achieve?

      Platform teams currently use a variety of mechanisms for inner-loop testing on their local development machine. All teams should instead use Docker images for most local testing, with real clusters used where needed on Evergreen for CI validation.

      Traditional local development is greatly improved by a fast inner-loop. That is, by making the time needed to compile and test code as short as possible, so that changes can rapidly be iterated on. This requires fast local tests.

      AI agents also expect to be able to run tests locally, and will do so as part of their development loop. This adds even more benefit to being able to run tests easily and quickly for local development.

      Motivation

      Who is the affected end user?

      Driver teams and external contributors, as well as AI agents.

      How does this affect the end user?

      It is currently difficult for external contributors to contribute to our driver repos; this should make it much easier. Also, it will allow rapid execution of tests by developers and agents, leading to a faster inner-loop.

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

      N/A

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

      N/A

      Is this issue urgent?

      No

      Is this ticket required by a downstream team?

      No

      Is this ticket only for tests?

      Yes

      Cast of Characters

      Engineering Lead: arthur.vickers@mongodb.com 
      Document Author:
      POCers:
      Product Owner:
      Program Manager:
      Stakeholders:

      Channels & Docs

      Slack Channel: #dbx-devs

      [Scope Document|some.url]

      [Technical Design Document|some.url]

            Assignee:
            Arthur Vickers
            Reporter:
            Arthur Vickers
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None
              None
              None