[EPIC] Increase Test Coverage
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react-native, typescript
Research direction
This epic groups tests for state and contexts, UI components, and app screens into sub-issues #122–#141. Start by choosing a sub-issue, then review the existing tests in src/utils/__tests__ and src/store/__tests__ for Jest and React Native Testing Library patterns. Done means the selected sub-issue’s major components, context, or screens have the requested tests.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Our overall test coverage is currently low (~18%). While core utilities are tested, many components and screens remain untested. To ensure app stability and prevent regressions, we need to increase our test coverage across the whole project.
Describe the solution you'd like
We need to add unit and component tests for all major components, contexts, and screens using Jest and React Native Testing Library. This is an Epic that groups several sub-tasks.
Writing tests is one of the best and safest ways to contribute to open source! Pick a sub-issue below to help out.
Sub-Modules (Claim yours!)
Module 1: State & Contexts
- #122
- #123
- #124
Module 2: Core UI Components
- #125
- #126
- #127
- #128
- #129
- #130
Module 3: Complex UI Components
- #131
- #132
- #133
- #134
Module 4: App Screens
- #135
- #136
- #137
- #138
- #139
- #140
- #141
Describe alternatives you've considered
N/A - Automated testing is a standard requirement for robust applications.
Additional Context
- We use Jest and React Native Testing Library.
- Check the existing tests in
src/utils/__tests__andsrc/store/__tests__for inspiration on how we mock timers and storage.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GiZano/LevelUp
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·