Updating and documenting Unit Test and Component norms

chris-kuryak commented 11 months ago

Problem statement

Testing components currently is difficult (requires more code to test) due to components fetching data and processing it. If we separate these into distinct responsibilities it will make it easier to test the core programming that is in the processing side.

What you need to know

Acceptance criteria

[ ] Proposal documents created for unit tests and component norms (including when to write unit tests and where they should be documented)
[ ] Project updated to conform to those new norms
[ ] All current tests still pass

chris-kuryak commented 9 months ago

Est capacity needed to finish ~5 days

chris-kuryak commented 8 months ago

Blocked by #10850

Then need to move Settings form moved to one codebase -- this will help with all testing (including E2E testing). #12447 Followed by documenting our norms.

chris-kuryak commented 7 months ago

Pausing to waiting on conversation about moving away from our SPA framework

CDCgov / prime-reportstream