|
Some checks failed
Deploy Development / deploy (push) Successful in 39s
Test Suite / pytest-backend (push) Successful in 35s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 12s
Test Suite / playwright-tests (push) Failing after 5s
- Added a new job to the Gitea CI workflow to install k6 and run health baseline tests after the health wait period. - Updated documentation to reflect the automatic execution of k6 in the CI pipeline and clarified local execution instructions. - Enhanced architecture documentation to indicate the completion of Phase 0 for the pipeline part, with k6 running after each relevant deploy. |
||
|---|---|---|
| .. | ||
| k6-health-baseline.js | ||
| README.md | ||
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
Aufruf Beispiel
# Windows PowerShell
$env:BASE_URL="https://dev.shinkan.jinkendo.de"
k6 run scripts/load/k6-health-baseline.js
# Linux / macOS
BASE_URL=https://dev.shinkan.jinkendo.de k6 run scripts/load/k6-health-baseline.js
Wenn BASE_URL fehlt, nutzt das Skript die Default-URL im Script (anpassen bei Bedarf).
Auswertung
In der k6-Zusammenfassung http_req_duration → p(95) in BASELINE_SNAPSHOT.md eintragen.
Schwellwerte sind bewusst locker (p95 < 3s); bei Fehlschlag Proxy, Netz oder Backend prüfen.