Use Case

As a driver engineer,
I want type safety in our critical test tooling,
So that I can make changes with confidence.

Compiling our test suite might be a great end goal, but fixing all compiler errors properly in our test suite would make the process very time consuming.

We might be able to get a lot of benefit of compiling only certain files though.  Specifically, compiling all our test runners and utilities would at least guarantee that we are catching potential issues with our test runners.

User Experience

• n/a

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

• 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