Lars
ebad8025f4
All checks were successful
Deploy Development / deploy (push) Successful in 38s
Test Suite / pytest-backend (push) Successful in 35s
Test Suite / lint-backend (push) Successful in 1s
Test Suite / build-frontend (push) Successful in 13s
Test Suite / playwright-tests (push) Successful in 1m30s
- Modified the k6 installation script in the Gitea CI workflow to dynamically select the appropriate binary for linux-amd64 or linux-arm64 based on the system architecture. - Updated README.md to reflect the changes in architecture handling for k6 installation, providing clearer guidance for users on different platforms.
31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
# k6 – Health-Baseline (Phase 0)
|
||
|
||
Parallele GETs auf `/health` – **ohne** Auth, geeignet für Dev/Prod hinter dem gleichen Proxy wie die App.
|
||
|
||
**CI / Deploy:** In **`.gitea/workflows/test.yml`** (Job `playwright-tests`): nach **/health-Wartezeit** läuft **k6** automatisch, danach Playwright. Gleiche `BASE_URL` wie E2E (Dev oder Prod nach `workflow_run`). Kein manueller Schritt nach dem Deploy.
|
||
|
||
## Voraussetzung
|
||
|
||
[k6 installieren](https://k6.io/docs/getting-started/installation/).
|
||
|
||
## Aufruf Beispiel
|
||
|
||
```bash
|
||
# Windows PowerShell
|
||
$env:BASE_URL="https://dev.shinkan.jinkendo.de"
|
||
k6 run scripts/load/k6-health-baseline.js
|
||
```
|
||
|
||
```bash
|
||
# Linux / macOS
|
||
BASE_URL=https://dev.shinkan.jinkendo.de k6 run scripts/load/k6-health-baseline.js
|
||
```
|
||
|
||
**Architektur:** Der Workflow lädt **linux-amd64** oder **linux-arm64** je nach `uname -m` (z. B. Gitea-Runner auf Raspberry Pi 5).
|
||
|
||
## Auswertung
|
||
|
||
In der k6-Zusammenfassung `http_req_duration` → **p(95)** in [BASELINE_SNAPSHOT.md](../../docs/architecture/BASELINE_SNAPSHOT.md) eintragen.
|
||
|
||
Schwellwerte sind bewusst locker (`p95 < 3s`); bei Fehlschlag Proxy, Netz oder Backend prüfen.
|