[EPIC] Increase Test Coverage

Open
#121 0 comments 0 reactions 0 assignees View on GitHub

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
Domain
mobile, testing

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

enhancement good first issue help wanted

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__ 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GiZano/LevelUp

All issues in GiZano/LevelUp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.