screen-locker/web/src/App.test.tsx
Krzysztof kuhy Rudnicki 8f911585c1 Serve the lock decision, its history and its health at 127.0.0.1:8770
The only status surface was a GTK tray icon, commented out of ~/.config/i3
on 2026-08-21. So when the weekly count went wrong, nothing on the machine
said so for two weeks -- the same silence that let a deleted timer job stop
enforcement for thirteen days in August.

Three read-only endpoints, and a React 19 UI over them:

  /api/status     the decision, the week, and whether today has a workout
  /api/decisions  the recorded trail, newest first
  /api/health     timers armed, disarm marker, log and trail freshness

The Why view is the one that matters: it renders the run of
"weekly_minimum_met 5/5" ticks that hid this week's bug, without anyone
having to reach for journalctl.

/api/status also carries gaming.workout_today, which is the fact
steam-backlog-enforcer will cut the daily budget on. Deliberately just the
fact -- the enforcer owns the hour values, so the two repos cannot come to
disagree about what a workout day is. It is derived from count_day_credits,
the same rule the locker enforces with.

_compliance_state_word moves from status_view (tkinter) into
_status_projection, and the systemd arming check moves from
scripts/check_enforcement_armed.py into screen_locker/_armed_state.py, so
the server can answer "is enforcement armed" without a second copy of the
logic that would be free to disagree with the gate.

web/ mirrors steam-backlog-enforcer/web but tightens it: that config has no
"strict" in any tsconfig, extends only tseslint recommended (no type-aware
rules at all), and gates neither lint nor typecheck in pre-commit. Here all
three run, on strictTypeChecked + stylisticTypeChecked, with
noUncheckedIndexedAccess and exactOptionalPropertyTypes. 44 tests, 100% of
statements, branches, functions and lines.

typescript stays pinned at 6.0.3: 7.0.2 is out, but every published
typescript-eslint -- stable, canary and rc-v8 -- declares
typescript ">=4.8.4 <6.1.0". The fleet allowlist already carries that entry.

The 250-line cap now covers ts/tsx. It was python/shell/dart only, which
would have made web/ exempt from the gate the rest of the repo lives under
-- the same omission that exempted the whole Flutter app until 2026-08-15.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fcwu78wk17FWMHbbfbyicc
2026-08-29 22:50:19 +02:00

54 lines
1.8 KiB
TypeScript

import { render, screen, waitFor } from '@testing-library/react'
import { afterEach, describe, expect, it, vi } from 'vitest'
import { App } from './App'
import { makeDecisions, makeHealth, makeStatus } from './test/factories'
function stubEndpoints(overrides: Record<string, unknown> = {}): void {
vi.stubGlobal(
'fetch',
vi.fn((url: string) => {
const body =
url.startsWith('/api/status')
? (overrides.status ?? makeStatus())
: url.startsWith('/api/health')
? (overrides.health ?? makeHealth())
: (overrides.decisions ?? makeDecisions())
return Promise.resolve({ ok: true, json: () => Promise.resolve(body) })
}),
)
}
afterEach(() => {
vi.unstubAllGlobals()
})
describe('App', () => {
it('renders all three views once the endpoints answer', async () => {
stubEndpoints()
render(<App />)
await waitFor(() => {
expect(screen.getByRole('heading', { name: 'Now' })).toBeInTheDocument()
})
expect(screen.getByRole('heading', { name: 'Health' })).toBeInTheDocument()
expect(screen.getByRole('heading', { name: 'Why' })).toBeInTheDocument()
})
it('shows a loading line before the first status arrives', () => {
vi.stubGlobal('fetch', vi.fn(() => new Promise(() => undefined)))
render(<App />)
expect(screen.getByText('Reading status…')).toBeInTheDocument()
})
it('surfaces a failing endpoint instead of silently showing nothing', async () => {
vi.stubGlobal(
'fetch',
vi.fn().mockResolvedValue({ ok: false, status: 503, statusText: 'Unavailable' }),
)
render(<App />)
await waitFor(() => {
expect(screen.getByRole('alert')).toBeInTheDocument()
})
expect(screen.getByRole('alert')).toHaveTextContent('API returned 503')
})
})