CU - Improve unit test coverage, part 10 - Githubissues

department-of-veterans-affairs / va-mobile-app

"If VA were a company, it would have a flagship mobile app."

https://department-of-veterans-affairs.github.io/va-mobile-app/

17 stars 2 forks source link

CU - Improve unit test coverage, part 10 #10181

Open alexandec opened 1 week ago

alexandec commented 1 week ago

Proposed Change

Improve unit test coverage for the following files (current coverage is shown):

src/screens/HealthScreen/Appointments/UpcomingAppointments/UpcomingAppointmentDetails.tsx: 44.61% src/api/appointments/cancelAppointment.tsx: 45.45%

See our test coverage best practices for important considerations around coverage.

Why Should We Prioritize?

Improved test coverage helps us catch regressions faster, reducing development time and cutting down on bug frequency.

Coding Time Estimation

3

Testing Considerations

Passing unit tests with appropriate coverage constitutes success.

Checklist

[ ] Add the relevant team label (Health, global, design system, API, Qa and Release etc.)
[ ] Attach to ticket to the relevant Team Tech Debt Epic epic (old frontend engineering epic is no longer in use as each team is managing their code's technical debt and code upkeep work)