mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-11 13:52:20 +00:00
* Revert "revert: roll source tree back to v1.4.0 to restore production"
This reverts commit e444a90b10.
* fix(v1.4.2): summaries.WEIGHT + medications array guards + healthcheck IPv4
Three production bugs surfaced after the v1.4.0 deploy stabilized:
1. `TypeError: undefined is not an object (evaluating 'E?.summaries.WEIGHT')`
on /dashboard and /insights for users without weight readings —
the optional chain stopped at `data` when it needed to also cover
`data.summaries`. Fixed: `data?.summaries?.WEIGHT` (one level deeper).
2. `TypeError: y?.filter is not a function` on /medications — the
medications query value was non-array (likely a stale
service-worker response from an older API shape). Replaced with
`Array.isArray(medications) ? medications : []` so the page is
immune to any future shape drift.
3. Healthcheck-induced 503 outage (already in 1.4.1 — included here
so 1.4.2 is the single coherent release). The docker-compose
healthcheck used `localhost` which busybox-wget resolves to IPv6
::1; Next.js standalone listens on IPv4 0.0.0.0 only. Pinned
to 127.0.0.1.
This release also includes everything from v1.4.1 (which never
published a clean GHCR tag): the per-section admin extraction, the
testcontainers integration suite, the Playwright + axe-core E2E
foundation, the moodLog SSRF fix, the central error-redaction in
WideEventBuilder + Glitchtip, the medical-citation drift fixes
(ESH 2023, Saint-Maurice attribution, steps source), and the docs
sync.
Co-Authored-By: Marc-André Bombeck <mbombeck@gmail.com>
54 lines
1.8 KiB
TypeScript
54 lines
1.8 KiB
TypeScript
import { expect, test } from "@playwright/test";
|
|
|
|
/**
|
|
* Smoke checks on the login surface — must render, must wire the
|
|
* password-manager autofill hints (autoComplete="username" /
|
|
* "current-password"), must let the user submit.
|
|
*
|
|
* These do NOT log in (no DB seed required); the password-flow
|
|
* roundtrip is exercised by the integration test in
|
|
* tests/integration/auth-flow.test.ts.
|
|
*/
|
|
test.describe("login page", () => {
|
|
test("renders username + password inputs with the right autoComplete", async ({
|
|
page,
|
|
}) => {
|
|
await page.goto("/auth/login");
|
|
|
|
const username = page.getByLabel(/username|benutzername/i).first();
|
|
await expect(username).toBeVisible();
|
|
await expect(username).toHaveAttribute("autoComplete", /username|email/);
|
|
|
|
const password = page.locator('input[type="password"]').first();
|
|
await expect(password).toBeVisible();
|
|
await expect(password).toHaveAttribute("autoComplete", "current-password");
|
|
});
|
|
|
|
test("rejects an obviously-wrong credential pair", async ({ page }) => {
|
|
await page.goto("/auth/login");
|
|
|
|
await page
|
|
.getByLabel(/username|benutzername/i)
|
|
.first()
|
|
.fill("nobody-here");
|
|
await page.locator('input[type="password"]').first().fill("not-the-pw");
|
|
|
|
// Intercept the API call so the test does not depend on a real
|
|
// backend rejecting the credentials. The login form's error
|
|
// surfacing is what we actually want to prove here.
|
|
await page.route("**/api/auth/login", (route) =>
|
|
route.fulfill({
|
|
status: 401,
|
|
contentType: "application/json",
|
|
body: JSON.stringify({ error: "Invalid credentials" }),
|
|
}),
|
|
);
|
|
|
|
await page.getByRole("button", { name: /login|anmelden|sign in/i }).click();
|
|
|
|
await expect(
|
|
page.getByText(/invalid credentials|ungültig|falsch/i),
|
|
).toBeVisible({ timeout: 5_000 });
|
|
});
|
|
});
|