[SERVER-68362] Create Test Fixture for RemoteCommandRunner Testing Infra Created: 27/Jul/22 Updated: 05/Dec/22 Resolved: 03/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Erin McNulty | Assignee: | Backlog - Service Architecture |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
Right now, a lot of testing setup (task executor, network env, opctx) is duplicated between the hedged_remote_command runner test and the remote_command_runner tests.
It might be useful to put that logic in one unified file to make future testing with our API easier to do out of the box. |
| Comments |
| Comment by Jason Chan [ 03/Oct/22 ] |
|
This was done as part of the adding scaffolding for mock remote command runner commit of |