Use Case

The test:
CSOT State machine #markCommand when csot is enabled and markCommand() takes longer than the remaining timeoutMS the command should fail due to a timeout error

Sometimes succeeds, but there is a sleep stubbed in for sendCommand that is equal to timeoutMS. We should always timeout when we call the real sendCommand after the sleep because we've used up the time during the sleep.

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

• Determine why markCommand is able to succeed even though we've slept for timeoutMS

Testing Requirements

• unit test, spec test sync, etc

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