Use Case

As a...Node.js engineer
I want... coverage to wait on tasks that actually contribute to coverage
So that... I can verify coverage changes when they are ready

Developer Experience

• Coverage only waits on tasks that upload coverage results

Dependencies

• None

Risks/Unknowns

• At least exempting the now slow performance tasks would be good, but how can we make coverage accurately wait on only coverage contributing tasks? (ex. not eslint)
• Should coverage be something we run when needed?

Acceptance Criteria

Implementation Requirements

• Remove coverage dependence on perf tasks

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