There is a suite of spec tests to cover this for timeoutMS.
------------------------

Use Case

As a... Node.js driver user
I want... timeoutMS to be preferred over deprecated options
So that... I get consistent new behavior if I accidentally specify both the new and the old options.

User Experience

• The timeoutMS option should be preferred over all options listed here: https://github.com/mongodb/specifications/blob/master/source/client-side-operations-timeout/tests/deprecated-options.yml
• All options that are required to be deprecated by CSOT should be marked deprecated in the driver.

Dependencies

• None

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
  • N/A
• Is there an opportunity for better cross-driver alignment or testing in this area?
  • Already tested by spec
• Is there an opportunity to improve existing documentation on this subject?
  • We should double check the node driver mongodb docs to make sure the deprecated options are marked accordingly

Acceptance Criteria

Implementation Requirements

• Deprecate anything that CSOT marks deprecated
• Add logic to ensure timeoutMS is preferred over the deprecated options

Testing Requirements

• Spec tests here: https://github.com/mongodb/specifications/blob/master/source/client-side-operations-timeout/tests/deprecated-options.yml

Documentation Requirements

• API docs for deprecations
• Manual docs as needed

Follow Up Requirements

• File bug ticket to do this more generally for other options