feat(ci): integrate k6 health baseline testing into Gitea workflow
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
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.
This commit is contained in:
1 parent
4b2848c7c3
commit
c7650cac2f
3 files changed
+23
-3
No files matched your search
@@ -2,6 +2,8 @@
|
||||
|
||||
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/).
|
||||
@@ -16,7 +18,6 @@ k6 run scripts/load/k6-health-baseline.js
|
||||
|
||||
```bash
|
||||
# Linux / macOS
|
||||
```bash
|
||||
BASE_URL=https://dev.shinkan.jinkendo.de k6 run scripts/load/k6-health-baseline.js
|
||||
```
|
||||
|
||||
|
||||
Reference in new issue
Block a user