Keep the dev deploy and the test suite as separate workflows.
Deploy Development / deploy (push) Successful in 59s
Test Suite / pytest-backend (push) Successful in 49s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 16s
Test Suite / k6 /health Baseline (push) Successful in 43s
Test Suite / playwright-tests (push) Failing after 7m54s

Tests no longer run as jobs inside the development deploy. A push to develop starts the test suite on its own and aims it at the dev stack.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
LarsandCursor committed 2026-10-28 13:54:42 +01:00
1 parent 5fc839afbc
commit ad7c7ad4e5
2 files changed
+7 -110

No files matched your search

+1 -104
View File
@@ -1,6 +1,4 @@
# Name bewusst nicht "Deploy Development": die Test-Suite auf main lauscht auf
# diesen alten Namen und fällt ohne erkannten Workflow-Namen auf das Prod-Verzeichnis.
name: Deploy Dev Stack
name: Deploy Development
on:
push:
@@ -28,104 +26,3 @@ jobs:
echo "✓ DEV API healthy"
curl -sf http://localhost:3098/api/version && echo "✓ DEV über Frontend-Nginx (wie Browser) healthy"
echo "=== Shinkan DEV Deploy complete ==="
pytest-backend:
needs: deploy
runs-on: ubuntu-latest
steps:
- name: Backend pytest im Dev-Container
run: sh /home/lars/docker/shinkan-dev/scripts/ci/run-deployed-checks.sh dev pytest
lint-backend:
needs: deploy
runs-on: ubuntu-latest
steps:
- name: Check backend syntax
run: sh /home/lars/docker/shinkan-dev/scripts/ci/run-deployed-checks.sh dev lint
build-frontend:
needs: deploy
runs-on: ubuntu-latest
steps:
- name: Build frontend
run: sh /home/lars/docker/shinkan-dev/scripts/ci/run-deployed-checks.sh dev frontend
k6-health-baseline:
name: k6 /health Baseline
needs: deploy
runs-on: ubuntu-latest
steps:
- name: k6 gegen Dev
run: sh /home/lars/docker/shinkan-dev/scripts/ci/run-deployed-checks.sh dev k6
playwright-tests:
needs: deploy
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "20"
- name: Dev /health
run: |
BASE="https://dev.shinkan.jinkendo.de"
echo "Warte auf $BASE/health …"
for i in $(seq 1 90); do
if curl -sf "$BASE/health" >/dev/null 2>&1; then
echo "Health OK (Versuch $i)"
exit 0
fi
sleep 2
done
echo "Timeout: Dev /health nicht erreichbar"
curl -v "$BASE/health" || true
exit 1
- name: Testnutzer registrieren
env:
E2E_DEV_TEST_EMAIL: ${{ secrets.E2E_DEV_TEST_EMAIL }}
E2E_DEV_TEST_PASSWORD: ${{ secrets.E2E_DEV_TEST_PASSWORD }}
run: |
BASE="https://dev.shinkan.jinkendo.de"
if [ -z "$E2E_DEV_TEST_EMAIL" ] || [ -z "$E2E_DEV_TEST_PASSWORD" ]; then
echo "(Registrierung übersprungen — Secrets E2E_DEV_* nicht gesetzt.)"
exit 0
fi
curl -sf -X POST "$BASE/api/auth/register" \
-H "Content-Type: application/json" \
-d "{\"email\":\"${E2E_DEV_TEST_EMAIL}\",\"password\":\"${E2E_DEV_TEST_PASSWORD}\",\"name\":\"Playwright CI\"}" \
|| echo "(Register evtl. schon erfolgt oder Limits — Login-Test gilt trotzdem.)"
- name: Install Playwright
run: |
npm ci || npm install
npx playwright install --with-deps chromium
- name: Run Playwright tests
env:
E2E_DEV_TEST_EMAIL: ${{ secrets.E2E_DEV_TEST_EMAIL }}
E2E_DEV_TEST_PASSWORD: ${{ secrets.E2E_DEV_TEST_PASSWORD }}
PLAYWRIGHT_BASE_URL: https://dev.shinkan.jinkendo.de
run: |
set -e
export TEST_EMAIL="$E2E_DEV_TEST_EMAIL"
export TEST_PASSWORD="$E2E_DEV_TEST_PASSWORD"
if [ -z "$TEST_EMAIL" ] || [ -z "$TEST_PASSWORD" ]; then
echo "Fehler: E2E_DEV_TEST_EMAIL und E2E_DEV_TEST_PASSWORD setzen."
exit 1
fi
mkdir -p screenshots
npx playwright test
echo "Playwright tests passed"
- name: Upload test screenshots
if: failure()
uses: actions/upload-artifact@v3
with:
name: playwright-screenshots
path: screenshots/
retention-days: 7
+6 -6
View File
@@ -1,12 +1,12 @@
name: Test Suite
# Dev-Tests hängen an "Deploy Dev Stack" (deploy-dev.yml) und laufen nach dem Deploy
# gegen /home/lars/docker/shinkan-dev. Dieser Workflow hier startet sie nicht noch einmal.
#
# workflow_run läuft mit der Datei auf dem Standardbranch (main). Ein Dev-Deploy darf
# hier nicht landen: ohne erkannten Namen fiel das Skript auf das Prod-Verzeichnis.
# Produktion nur, wenn der auslösende Workflow exakt "Deploy Production" heißt.
# Eigener Workflow, getrennt von Deploy Development.
# push/PR auf develop: diese Datei, Ziel ist das Testsystem.
# workflow_run nur nach Deploy Production. Nicht nach dem Dev-Deploy:
# der Listener auf main nutzt bei fehlendem Namen sonst das Prod-Verzeichnis.
on:
push:
branches: [develop]
pull_request:
branches: [develop]
workflow_run: