senke/veza
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
veza/tmt
History
senke 22e5e21757 chore(audit 2.4, 2.5): supprimer code mort Education et cmd/modern-server 
- Supprimer routes/handlers/core Education (backend)
- Supprimer handler MSW education, refs Sidebar/locales
- Basculer Makefile, make/dev.mk, scripts vers cmd/api/main.go
- Supprimer veza-backend-api/cmd/modern-server/
2026-02-15 14:39:40 +01:00
..
plans feat: global update including storybook setup and backend fixes 2026-02-02 19:34:14 +01:00
tests chore(audit 2.4, 2.5): supprimer code mort Education et cmd/modern-server 2026-02-15 14:39:40 +01:00
README.md feat: global update including storybook setup and backend fixes 2026-02-02 19:34:14 +01:00

README.md

Veza Unified Testing Pipeline (TMT)

Philosophy: Sobriety, Frugality, Accessibility. The Law: docs/FRUGALITY.md The Contract: docs/BUDGETS.md

This directory contains the definition of Veza's unified testing pipeline. It is the Executive Branch that enforcing the laws defined in FRUGALITY.md and BUDGETS.md.

🛑 The Rules

  1. VITAL Tests Block Everything: If a test in plans/vital.fmf fails, the commit is rejected.
  2. Contractual Budgets: Resource limits are defined in docs/BUDGETS.md. Tests verify these limits.
  3. No New Frontend Tests: By default, new frontend tests are legacy. You must prove a test is vital to promote it.

Directory Structure

  • plans/:
    • vital.fmf: TIER 1. The "must pass" suite. Runs fast, strictly, and enforces budgets.
    • legacy.fmf: TIER 2. Slow/Old tests. Informational only.
  • tests/: Actual test scripts.
    • frontend/: Linked to BUDGETS.md.
    • backend/: Linked to BUDGETS.md.
    • services/: Strict Rust checks.

How to Run

Vital Tests (The Standard)

tmt run plan --name /vital

Full Suite (Including Regressions/Legacy)

tmt run

Environment Variables

The pipeline enforces:

  • GOMAXPROCS=1: Simulate single-core environment.
  • LIBGL_ALWAYS_SOFTWARE=1: Disable GPU.