[SERVER-67612] Add skeleton of infrastructure for mocking runRemoteCommand Created: 28/Jun/22 Updated: 29/Oct/23 Resolved: 02/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | George Wangensteen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service Arch 2022-08-08, Service Arch 2022-08-22, Service Arch 2022-09-05, Service Arch 2022-09-19 | ||||||||
| Participants: | |||||||||
| 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. |
| Comments |
| Comment by Githook User [ 02/Sep/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |