veza/docs/archive/frontend-sessions-2026/PLAN_TESTS_PRIORITES.md
senke 0e7097ed1b chore(cleanup): J1 — purge 220MB debris, archive session docs (complete)
First-attempt commit 3a5c6e184 only captured the .gitignore change; the
pre-commit hook silently dropped the 343 staged moves/deletes during
lint-staged's "no matching task" path. This commit re-applies the intended
J1 content on top of bec75f143 (which was pushed in parallel).

Uses --no-verify because:
- J1 only touches .md/.json/.log/.png/binaries — zero code that would
  benefit from lint-staged, typecheck, or vitest
- The hook demonstrated it corrupts pure-rename commits in this repo
- Explicitly authorized by user for this one commit

Changes (343 total: 169 deletions + 174 renames):

Binaries purged (~167 MB):
- veza-backend-api/{server,modern-server,encrypt_oauth_tokens,seed,seed-v2}

Generated reports purged:
- 9 apps/web/lint_report*.json (~32 MB)
- 8 apps/web/tsc_*.{log,txt} + ts_*.log (TS error snapshots)
- 3 apps/web/storybook_*.json (1375+ stored errors)
- apps/web/{build_errors*,build_output,final_errors}.txt
- 70 veza-backend-api/coverage*.out + coverage_groups/ (~4 MB)
- 3 veza-backend-api/internal/handlers/*.bak

Root cleanup:
- 54 audit-*.png (visual regression baselines, ~11 MB)
- 9 stale MVP-era scripts (Jan 27, hardcoded v0.101):
  start_{iteration,mvp,recovery}.sh,
  test_{mvp_endpoints,protected_endpoints,user_journey}.sh,
  validate_v0101.sh, verify_logs_setup.sh, gen_hash.py

Session docs archived (not deleted — preserved under docs/archive/):
- 78 apps/web/*.md     → docs/archive/frontend-sessions-2026/
- 43 veza-backend-api/*.md → docs/archive/backend-sessions-2026/
- 53 docs/{RETROSPECTIVE_V,SMOKE_TEST_V,PLAN_V0_,V0_*_RELEASE_SCOPE,
          AUDIT_,PLAN_ACTION_AUDIT,REMEDIATION_PROGRESS}*.md
                        → docs/archive/v0-history/

README.md and CONTRIBUTING.md preserved in apps/web/ and veza-backend-api/.

Note: The .gitignore rules preventing recurrence were already pushed in
3a5c6e184 and remain in place — this commit does not modify .gitignore.

Refs: AUDIT_REPORT.md §11
2026-04-14 17:12:03 +02:00

131 lines
3.4 KiB
Markdown

# Plan d'Amélioration des Tests - Priorités
**Date:** 2025-01-27
**Objectif:** Atteindre 80%+ de couverture de tests
---
## 📊 État Actuel
### Tests Existants
-**98 fichiers** de tests passent
- ⚠️ **163 fichiers** de tests échouent (à corriger)
-**2305 tests** passent
- ⚠️ **683 tests** échouent (à corriger)
### Problèmes Identifiés
1. **React Router Context** - `basename` null dans certains tests
2. **showError** non défini dans certains composants
3. **Setup de tests** - Besoin d'améliorer les mocks
---
## 🎯 Plan d'Action Priorisé
### Phase 1: Corriger les Tests Existants (PRIORITÉ CRITIQUE)
**Objectif:** Faire passer tous les tests existants avant d'en ajouter
#### 1.1. Corriger Setup de Tests
- [ ] Ajouter BrowserRouter dans setup de tests
- [ ] Corriger mocks pour React Router
- [ ] Ajouter mocks pour showError/toast
#### 1.2. Corriger Tests Échouants
- [ ] `PlaylistBatchActions.test.tsx` - showError non défini
- [ ] `TrackSearch.test.tsx` - React Router context manquant
- [ ] Autres tests avec erreurs similaires
**Estimation:** 2-3 jours
---
### Phase 2: Tests Composants UI Critiques (PRIORITÉ HAUTE)
**Objectif:** Couvrir les composants UI les plus utilisés
#### Composants à Tester (28 composants sans tests)
**Semaine 1-2: Composants Formulaires**
- [ ] `input.tsx` - Composant critique
- [ ] `checkbox.tsx` - Composant critique
- [ ] `textarea.tsx` - Composant critique
- [ ] `label.tsx` - Composant critique
- [ ] `radio-group.tsx` - Composant critique
- [ ] `switch.tsx` - Composant critique
**Semaine 3-4: Composants Feedback**
- [ ] `alert.tsx` - Composant critique
- [ ] `progress.tsx` - Composant critique
- [ ] `Toast.tsx` - Composant critique
- [ ] `empty-state.tsx` - Composant critique
**Semaine 5-6: Composants Navigation**
- [ ] `tabs.tsx` - Composant critique
- [ ] `table.tsx` - Composant critique
- [ ] `scroll-area.tsx` - Composant critique
- [ ] `slider.tsx` - Composant critique
**Estimation:** 6 semaines
---
### Phase 3: Tests Services (PRIORITÉ HAUTE)
**Objectif:** Couvrir la logique métier
#### Services à Tester (17 services sans tests)
- [ ] `adminService.ts`
- [ ] `analyticsService.ts`
- [ ] `chatService.ts`
- [ ] `commerceService.ts`
- [ ] `developerService.ts`
- [ ] `educationService.ts`
- [ ] `gamificationService.ts`
- [ ] `gearService.ts`
- [ ] `groupService.ts`
- [ ] `playlistService.ts`
- [ ] `projectService.ts`
- [ ] `searchService.ts`
- [ ] `sessionService.ts`
- [ ] `socialService.ts`
- [ ] `storageService.ts`
- [ ] `uploadService.ts`
- [ ] `userService.ts`
**Estimation:** 4-5 semaines
---
### Phase 4: Tests Context & Hooks (PRIORITÉ MOYENNE)
**Objectif:** Couvrir la gestion d'état
#### Context à Tester (5 fichiers)
- [ ] `AudioContext.tsx`
- [ ] `AuthContext.tsx`
- [ ] `CartContext.tsx`
- [ ] `ThemeContext.tsx`
- [ ] `ToastContext.tsx`
**Estimation:** 2 semaines
---
## 📈 Métriques de Succès
### Objectifs
-**100% des tests existants passent**
-**80%+ couverture globale**
-**90%+ couverture pour composants UI critiques**
-**80%+ couverture pour services**
---
## 🚀 Prochaines Étapes Immédiates
1. ⏳ Corriger setup de tests (React Router, mocks)
2. ⏳ Corriger tests échouants existants
3. ⏳ Créer tests pour composants UI critiques
4. ⏳ Créer tests pour services manquants
5. ⏳ Générer rapport de couverture
---
**Dernière mise à jour:** 2025-01-27