veza/tmt/README.md
senke ad60247f33 feat: global update including storybook setup and backend fixes
- Web: Setup Storybook, added addons, configured Tailwind, added stories for UI components.
- Backend: Updated API router, database, workers, and auth in common.
- Stream Server: Removed SQLx queries and updated auth.
- Docs & Scripts: Updated documentation and recovery scripts.
2026-02-02 19:34:14 +01:00

41 lines
1.4 KiB
Markdown

# Veza Unified Testing Pipeline (TMT)
> **Philosophy**: Sobriety, Frugality, Accessibility.
> **The Law**: [docs/FRUGALITY.md](../docs/FRUGALITY.md)
> **The Contract**: [docs/BUDGETS.md](../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)
```bash
tmt run plan --name /vital
```
### Full Suite (Including Regressions/Legacy)
```bash
tmt run
```
## Environment Variables
The pipeline enforces:
- `GOMAXPROCS=1`: Simulate single-core environment.
- `LIBGL_ALWAYS_SOFTWARE=1`: Disable GPU.