[CXX-1265] Audit driver against Max Staleness Spec Created: 20/Mar/17  Updated: 11/Aug/17  Resolved: 02/Jun/17

Status: Closed
Project: C++ Driver
Component/s: Testing
Affects Version/s: None
Fix Version/s: 3.2.0-rc0

Type: Task Priority: Major - P3
Reporter: David Golden Assignee: Samuel Rossi (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to CXX-1357 Add test and implementation for max s... Closed
Epic Link: CXX-1293

 Description   

Revalidate driver against:



 Comments   
Comment by Samuel Rossi (Inactive) [ 02/Jun/17 ]

We already have a test for setting a positive value less than 90, but we do not have any tests regard the URI option for max staleness, so I've filed CXX-1357 to track that.

Comment by David Golden [ 02/Jun/17 ]

I think we should have tests that verify (if we don't already):

  • That setting a positive value < 90 seconds is not an error at the time set
  • That setting it to -1 in the connection string indeed causes our getter to return nullopt

Otherwise, we can rely on the C driver.

Comment by Samuel Rossi (Inactive) [ 31/May/17 ]

The max staleness spec describes a number of tests (both prose and JSON). However, all of the functionality described by the spec (with the exception of providing users with a read preference setting for the max staleness in seconds) is implemented in the C driver rather than the C++ driver.

david.golden, is it worth implementing the tests for functionality only present in the C driver, or would be prefer to leave this to the C driver itself?

Generated at Wed Feb 07 22:01:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.