Use Case

As a driver maintainer of ESM-only packages,
I want to use code coverage tooling that supports ESM,
So that we can continue to get code coverage reports after switching to ESM.

User Experience

• n/a

Dependencies

• n/a

Risks/Unknowns

• n/a

Acceptance Criteria

Implementation Requirements

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

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