senke/veza
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
veza/docs/archive/v0-history/SMOKE_TEST_V0701.md
senke 7c9eece09a
Some checks failed
Backend API CI / test-unit (push) Has been cancelled
Details
Backend API CI / test-integration (push) Has been cancelled
Details
Veza CI / Rust (Stream Server) (push) Has been cancelled
Details
Veza CI / Backend (Go) (push) Has been cancelled
Details
Veza CI / Notify on failure (push) Has been cancelled
Details
Veza CI / Frontend (Web) (push) Has been cancelled
Details
Frontend CI / test (push) Has been cancelled
Details
Security Scan / Secret Scanning (gitleaks) (push) Has been cancelled
Details
chore(cleanup): J1 — purge 220MB debris, archive session docs (complete) 
First-attempt commit 02728909f 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 24af2f72b (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
02728909f 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
4.5 KiB
Markdown
Raw Blame History

# Smoke Test v0.701 — Retry Transfers, Admin Dashboard & Deep Health
**Objectif** : Valider toutes les fonctionnalités v0.701 et vérifier l'absence de régressions.
---
## Prérequis
- [ ] Backend Go compile sans erreur (`go build ./...`)
- [ ] Frontend build OK (`npm run build` dans `apps/web`)
- [ ] Base de données migrée (migration 116 appliquée)
- [ ] Variables d'environnement configurées : `TRANSFER_RETRY_ENABLED`, `TRANSFER_RETRY_MAX`, `TRANSFER_RETRY_INTERVAL_MIN`
---
## 1. Transfer Retry Worker (Lot R1)
### 1.1 Retry automatique
- [ ] Créer un SellerTransfer avec status `failed` en DB
- [ ] Démarrer le backend avec `TRANSFER_RETRY_ENABLED=true`
- [ ] Le worker retente le transfert dans le délai configuré
- [ ] En cas de succès : status passe à `completed`, retry_count incrémenté
- [ ] En cas d'échec : retry_count incrémenté, next_retry_at calculé (backoff exponentiel)
### 1.2 Max retries
- [ ] Un transfert avec retry_count >= max_retries n'est plus retenté
- [ ] Status passe à `permanently_failed`
### 1.3 Backoff exponentiel
- [ ] Délai entre retries augmente : base * 2^retry_count
- [ ] next_retry_at est correctement calculé et stocké
### 1.4 Prometheus metrics
- [ ] `veza_transfer_retry_total` est incrémenté à chaque tentative
- [ ] `veza_transfer_retry_success` est incrémenté en cas de succès
- [ ] `veza_transfer_retry_failures` est incrémenté en cas d'échec
---
## 2. Admin Transfers Dashboard (Lot A1)
### 2.1 Backend
- [ ] `GET /admin/transfers` retourne la liste paginée (200)
- [ ] Filtre par status fonctionne (`?status=failed`)
- [ ] Filtre par seller_id fonctionne (`?seller_id=uuid`)
- [ ] Filtre par date range fonctionne (`?from=...&to=...`)
- [ ] Pagination fonctionne (`?limit=10&offset=0`)
- [ ] Non-admin reçoit 403
### 2.2 Retry manuel
- [ ] `POST /admin/transfers/:id/retry` retry un transfert failed (200)
- [ ] Transfer non-failed retourne erreur appropriée (400)
- [ ] Transfer inexistant retourne 404
- [ ] Non-admin reçoit 403
### 2.3 Frontend
- [ ] Route `/admin/transfers` est accessible pour un admin
- [ ] Table affiche : seller, order, montant net, fee, status, retry_count, date
- [ ] Badge de status coloré (completed=vert, failed=rouge, permanently_failed=gris)
- [ ] Bouton Retry visible uniquement sur les transferts `failed`
- [ ] Clic Retry → appel API → table rafraîchie
- [ ] État Loading (skeleton) visible au chargement
- [ ] État Empty visible si aucun transfert
---
## 3. Deep Health Checks (Lot H1)
### 3.1 Endpoint
- [ ] `GET /health/deep` retourne JSON avec status global et par service
- [ ] DB healthy → ping réussi, latency_ms renseigné
- [ ] Redis healthy → ping réussi, latency_ms renseigné
- [ ] S3 indisponible → status `degraded` (pas unhealthy), error renseigné
- [ ] DB indisponible → status `unhealthy`
### 3.2 Startup validation
- [ ] JWT_SECRET vide → log fatal + exit
- [ ] DATABASE_URL invalide → log fatal + exit
- [ ] PLATFORM_FEE_RATE > 1 → log fatal + exit
- [ ] STRIPE_CONNECT_ENABLED=true sans STRIPE_SECRET_KEY → log warning
- [ ] En mode dev : warnings au lieu de fatals pour configs non-critiques
### 3.3 Prometheus
- [ ] `veza_health_check_status` gauge exposé par service (1=healthy, 0=unhealthy)
---
## 4. Documentation API (Lot D1)
- [ ] `docs/API_REFERENCE.md` existe et couvre les endpoints clés
- [ ] Exemples curl pour auth (login, register)
- [ ] Exemples curl pour marketplace (products, orders)
- [ ] Exemples curl pour admin (transfers)
- [ ] Exemples curl pour health (deep)
- [ ] `docs/MIGRATIONS.md` inclut migration 116
---
## 5. Flux existants (non-régressions)
### 5.1 Commerce
- [ ] Création de produit marketplace fonctionne
- [ ] Création de commande fonctionne
- [ ] Webhook payment succeeded → licences créées + transfer déclenché
### 5.2 Seller
- [ ] GET /sell/transfers retourne l'historique du vendeur (inchangé)
- [ ] SellerDashboard affiche les transferts (inchangé)
### 5.3 Auth
- [ ] Login/register fonctionnent
- [ ] JWT refresh fonctionne
### 5.4 Backend
- [ ] `go test ./...` — tous les tests passent
- [ ] GET /health retourne 200 (endpoint basique inchangé)
### 5.5 Frontend
- [ ] `npm run build` — build OK
- [ ] Storybook : AdminTransfersView stories sans erreur
---
## 6. Documentation & Release
- [ ] CHANGELOG.md mis à jour avec section v0.701
- [ ] PROJECT_STATE.md mis à jour
- [ ] FEATURE_STATUS.md mis à jour
- [ ] SCOPE_CONTROL.md pointe vers v0.702 (prochaine)
- [ ] RETROSPECTIVE_V0701.md créé
- [ ] Tag `v0.701` créé
Reference in a new issue View git blame Copy permalink