[EPIC] Increase Test Coverage

Aperta
#121 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react-native, typescript
Ambito
mobile, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
4
Fork
4
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di GiZano/LevelUp

Tutte le issue di GiZano/LevelUp

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.