[SERVER-40644] Add exhaustive feature tests for Split Horizon Created: 15/Apr/19  Updated: 27/Oct/23  Resolved: 16/May/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: ADAM Martin (Inactive) Assignee: Henrik Edin
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Dev Tools 2019-05-06, Dev Tools 2019-05-20
Participants:

 Description   

Test when the client explicitly asks (via horizonName) for something in the configuration.
Test when the client implicitly asks for something (via simulatedSniName or real SNI name) not in the configuration that the server replies with a valid isMaster response which appears as-if no horizon feature were present.
Test when the client implicitly asks for a horizon (via appName) not in the configuration that the server replies with a valid isMaster response which appears as-if no horizon feature were present.
Test when the client explicitly asks for something not in the configuration that an error is reported in the isMaster response.



 Comments   
Comment by Andrew Morrow (Inactive) [ 16/May/19 ]

This ticket was reflective of an earlier state of this project where a multitude of mechanism for horizon specification existed. As those were cut from scope, this ticket no longer represents specific work. Closing as gone away.

Comment by ADAM Martin (Inactive) [ 07/May/19 ]

In addition to the above (in description), we should setup another test variation which runs all replication tests while a split horizon is in effect (where the tests talk over the horizon entrypoint, not the local entrypoint).

Generated at Thu Feb 08 04:55:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.