Create more tickets for Jest testing

[andrea-williams]

Description of the Tech Debt

• [ ] write tickets breaking down Jest testing epic (#1174 )

Tech Debt Triage

The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level	Value
High	3
Medium	2
Low	1

Technical Debt - Risk Types	Level	Value
Business Area Risk - Risk of business area visibility / damage to user experience
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it
System Fault Risk - Risk of system errors or application downtime
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?
Time Sink Risk - How much will this tech debt slow the development process down
TOTAL SCORE:

[BCerki]

I've created the tickets listed below. Each contains a list of the files that need a jest test that are in scope of the ticket. Some notes:

• most our of page.tsx components don't do anything except render a single component. In these cases, I've only written tickets to test the components, not the actual page.tsx file.
• I didn't write what to test in the individual cards because we can address that with a team agreement (I'd rather not update the description of 16 cards individually as our strategy evolves). Here's a proposed strategy:

When testing simple (e.g., a confirmation message) components, assert:

• important/representative text or images .toBeVisible
• if applicable, when given different props, the component behaves as expected
• any clicks (buttons, dropdowns, accordions, etc.) do the correct action

When testing forms, assert:

• form renders correctly? (happo screenshot testing should cover label names, button visibility, etc. so maybe we don't need to this in jest?)
• when form data is valid (pass the form mock api response json via props), clicking next/submit does correct action (calls a function, redirects, etc.)
• when form data is invalid (empty or fields with required formats are wrong), clicking next/submit is unsuccessful and errors show up
• the form is editable/readonly when it's supposed to be (mock props/statuses/user roles/etc)
• if there's conditionality, it works

Here are the tickets:

• test the page.tsx components: https://github.com/bcgov/cas-registration/issues/1217
• test error/layout/not found components: https://github.com/bcgov/cas-registration/issues/1218
• simple component tests: https://github.com/bcgov/cas-registration/issues/1219, https://github.com/bcgov/cas-registration/issues/1220, https://github.com/bcgov/cas-registration/issues/1221
• form widgets: https://github.com/bcgov/cas-registration/issues/1222
• form components: https://github.com/bcgov/cas-registration/issues/1223
• select operator forms: https://github.com/bcgov/cas-registration/issues/1224
• user operator form: https://github.com/bcgov/cas-registration/issues/1226
• operations form: https://github.com/bcgov/cas-registration/issues/1225
• review forms: https://github.com/bcgov/cas-registration/issues/1227
• request access: https://github.com/bcgov/cas-registration/issues/1228
• operators page: https://github.com/bcgov/cas-registration/issues/1229
• profile form: https://github.com/bcgov/cas-registration/issues/1230
• operations components: https://github.com/bcgov/cas-registration/issues/1231
• select operator: https://github.com/bcgov/cas-registration/issues/1232 and https://github.com/bcgov/cas-registration/issues/1233
• utils: https://github.com/bcgov/cas-registration/issues/1234