[FEAT] Add tests for src/screens/ManageBlocksScreen.tsx
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react-native, typescript
Research direction
Start with src/screens/ManageBlocksScreen.tsx, then review existing tests in src/utils/__tests__ and src/store/__tests__ for test and mocking conventions. Add unit or component tests for rendering or initialization, relevant props and state changes, edge cases, and applicable user interactions; done when these behaviors are covered by passing 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%). To ensure app stability and prevent regressions, we need to increase test coverage across the codebase. This issue is part of the broader Epic to test Module 4: App Screens.
Describe the solution you'd like
Add unit/component tests for src/screens/ManageBlocksScreen.tsx using Jest and React Native Testing Library.
- Verify the component/hook renders or initializes correctly.
- Test props, state changes, and edge cases.
- Test user interactions if applicable.
Describe alternatives you've considered
N/A
Additional Context
This is a sub-task of #121 [EPIC] Increase Test Coverage.
Check the existing tests in src/utils/__tests__ and src/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 69/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
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 ·