Use Case

As a... (who is this for)
I want... (what is the desired change)
So that... (why is the change desired)

The CSOT unit test:
If timeoutMS is unset, operations fail after two non-consecutive socket timeouts.
isn't clear what is meant to happen, is the socket meant to be orchestrated in such a way that it would timeout for chunk0, not chunk1, and then again for chunk2 (assuming 3+ chunks of data?)

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• Add a comment noting that this is a spec unit test
• TBD

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward