Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-67612

Add skeleton of infrastructure for mocking runRemoteCommand

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Service Arch 2022-08-08, Service Arch 2022-08-22, Service Arch 2022-09-05, Service Arch 2022-09-19

    Description

      We want to be able to allow users to swap out the 'true' implementation of the remote command runner with a 'mock' implementation to make testing easy/remove dependency on a mocked network environment for testing. In this ticket, add the infrastructure to swap out the 'true' implementation for the mock; leave the mock as a stub for now - it will be implemented in a separate ticket. One idea is to use the ServiceContext as the site of dependency-injection, storing a pointer to a base class of both the real implementation and the mock. But it may be easier to locate the injection-point elsewhere and we should consider this during implementation.

      Attachments

        Activity

          People

            george.wangensteen@mongodb.com George Wangensteen
            george.wangensteen@mongodb.com George Wangensteen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: