[DRIVERS-2829] Create CSOT Legacy Timeout Analogues and Compatibility Field Created: 06/Feb/24  Updated: 06/Feb/24

Status: Needs Triage
Project: Drivers
Component/s: CSOT
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Preston Vasquez Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Driver Changes: Needed

 Description   

Summary

Drivers releasing a major version may opt to deprecate all legacy timeouts. This will result in legacy and unified tests listed here to fail.

Motivation

Who is the affected end user?

Drivers teams who are removing legacy timeouts in a major version.

How does this affect the end user?

NA

How likely is it that this problem or use case will occur?

100% likely during legacy timeout removal

If the problem does occur, what are the consequences and how severe are they?

Potentially lowers test coverage

Is this issue urgent?

Not urgent

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

Yes

Acceptance Criteria

1. Add CSOT analogues for unified tests defined here in specifications/source/client-side-operation-timeout/tests.

2. Bump the unified-test-format schema version to include a definitions.compatibilty field with the following structure:

"compatibilty": {
    "type": "array",
     "minItems": 0,
     "items": {
         "type": "string"
       }
},

compatibility should contain a list of reasons that a driver can chose to skip the test. In the specific use-case required by this ticket, drivers that no longer support legacy timeout options should be able to skip the compatibility requirement "legacy-timeout". It is currently unclear whether or not this field should be enumerated, as there is currently only one use case and this UST requirement has yet to come up in DBX.


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