Replace setupShards with addRemoteShards in all unit tests

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The setupShards() method is not enough if the tested code needs to send a request to a shard. In this case, tests will need to call `addRemoteShards()` instead.

      To provide a clean API and avoid confusion, I propose to get rid of `setupShards()` and always call `addRemoteShards()`, which includes the `setupShards()` plus the network setup for every shard.

            Assignee:
            Unassigned
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: