🐛 fix(frontend): apply server:false + route.fulfill to health spec (#43)
Some checks failed
CI/CD Pipeline / Build Docker Cache (push) Successful in 13s
CI/CD Pipeline / Trigger Docker Push (push) Has been cancelled
CI/CD Pipeline / CI Pipeline (push) Has been cancelled

Co-authored-by: Gabriel Radureau <arcodange@gmail.com>
Co-committed-by: Gabriel Radureau <arcodange@gmail.com>
This commit was merged in pull request #43.
This commit is contained in:
2026-05-05 09:04:48 +02:00
committed by arcodange
parent b33ad236e1
commit 4afc15b82e
3 changed files with 23 additions and 1 deletions

View File

@@ -1,6 +1,24 @@
import { test, expect } from '@playwright/test'
// Both specs mock /api/healthz so they decouple from the dev-proxy plumbing.
// The integration with the real backend is covered by the BDD scenario in
// features/health/health.feature (server-side, no frontend proxy in the loop).
// Same approach as tests/e2e/app-footer.spec.ts (PR #40) - applied here to
// close the debt left by that PR's out-of-scope follow-up note.
test('home page loads and shows healthy server state', async ({ page }) => {
await page.route('**/api/healthz', (route) => {
route.fulfill({
status: 200,
contentType: 'application/json',
body: JSON.stringify({
status: 'healthy',
version: '1.4.0',
uptime_seconds: 8042,
timestamp: '2026-05-05T08:00:00Z',
}),
})
})
await page.goto('/')
await expect(page.getByTestId('health-dashboard')).toBeVisible()
const heading = page.getByRole('heading', { name: /dance-lessons-coach/i })