feat(#376): e2e-web Drone-Step für Playwright-Smoke (Phase 3 E2E) #377
No reviewers
Labels
No labels
app/archiv
app/einkaufslisten
app/imap-client
app/wissensbasis
arch-answered
arch-question
area/api
area/auth
area/infra
area/mobile
area/shared
area/ui
area/web
portfolio-status
prio/high
prio/low
prio/medium
roadmap/public
size/l
size/m
size/s
size/xl
size/xs
status/blocked
status/needs-info
type/bug
type/chore
type/docs
type/feature
type/idea
type/refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
admin-mrrm/mrrmlabapp!377
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/376-e2e-drone-integration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #376
Stacked auf #375 — bitte erst #375 mergen, dann diesen PR (oder Base nach merge auf
mainumstellen).Summary
Führt den Playwright-Smoke-Test aus #375 im Drone-CI aus.
Was ändert sich
.drone.yml: neuer Stepe2e-webnachbuild-webin derci-Pipelinemcr.microsoft.com/playwright:v1.49.0-jammy(Chromium preinstalled, Version exakt zur lokalen@playwright/test1.49.0)depends_on: [build-web]— Sanity-Check, dass der Web-Build überhaupt gehtpnpm build && pnpm previewausplaywright.config.ts)workers=1+NODE_OPTIONS=--max-old-space-size=2048analog zubuild-web(OOM-Mitigation)Auth
Keine ENV-Vars im Drone-Step gesetzt →
VITE_KC_*leer beim webServer-Build → bestehender!auth-Pfad greift (login.tsx+requireAuthinrouter.tsx). Kein Test-Realm, kein Mock-Token.Nicht in diesem PR
Test plan
e2e-web-Step terminiert <5min, Smoke-Test passt🤖 Generated with Claude Code
041eaf9ad5a64e9c4252