[DRIVERS-779] Verify max set version and max election id on topologies in SDAM spec tests Created: 03/Dec/19  Updated: 02/Mar/21

Status: Implementing
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Esha Bhargava Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-3467 Verify max set version and max electi... Backlog
depends on PHPC-1516 Verify max set version and max electi... Closed
depends on PYTHON-2086 Verify max set version and max electi... Closed
depends on CXX-1895 Verify max set version and max electi... Backlog
depends on CSHARP-2881 Verify max set version and max electi... Closed
depends on GODRIVER-1445 Verify max set version and max electi... Closed
depends on JAVA-3559 Verify max set version and max electi... Closed
depends on MOTOR-481 Verify max set version and max electi... Closed
depends on NODE-2394 Verify max set version and max electi... Closed
depends on RUBY-2049 Verify max set version and max electi... Closed
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-3467 Backlog
JAVA-3559 Done
GODRIVER-1445 Fixed 1.4.0
PHPC-1516 Won't Fix
PYTHON-2086 Fixed 4.1
CXX-1895 Backlog
NODE-2394 Done 3.6.0
RUBY-2049 Duplicate
CSHARP-2881 Fixed 2.11.0
MOTOR-481 Works as Designed

 Description   

SDAM spec tests should verify max set version and max election id on topologies explicitly, as these attributes are publicly exposed per the spec.

https://github.com/mongodb/specifications/pull/409
https://github.com/mongodb/specifications/pull/417


Generated at Thu Feb 08 08:22:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.