Create Test Fixture for RemoteCommandRunner Testing Infra

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: