Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CU - Improve unit test coverage, part 13 #10184

Open
2 tasks
alexandec opened this issue Nov 13, 2024 · 0 comments
Open
2 tasks

CU - Improve unit test coverage, part 13 #10184

alexandec opened this issue Nov 13, 2024 · 0 comments
Labels
code upkeep front-end Ticket requires front-end work global Issues for the global team

Comments

@alexandec
Copy link
Contributor

alexandec commented Nov 13, 2024

Proposed Change

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

src/screens/HomeScreen/ProfileScreen/SettingsScreen/DeveloperScreen/RemoteConfigScreen.tsx: 50%
src/utils/rnReviews.tsx: 50%

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)
@alexandec alexandec added code upkeep front-end Ticket requires front-end work global Issues for the global team labels Nov 13, 2024
@alexandec alexandec changed the title Copy of CU - Improve unit test coverage, part 12 CU - Improve unit test coverage, part 13 Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code upkeep front-end Ticket requires front-end work global Issues for the global team
Projects
None yet
Development

No branches or pull requests

1 participant