screen-locker/web/src/useStatusPoll.test.ts
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

93 lines
2.9 KiB
TypeScript

import { renderHook, waitFor } from '@testing-library/react'
import { afterEach, describe, expect, it, vi } from 'vitest'
import { POLL_MS, usePoll } from './useStatusPoll'
afterEach(() => {
vi.useRealTimers()
})
describe('usePoll', () => {
it('loads immediately rather than waiting for the first interval', async () => {
const fetcher = vi.fn().mockResolvedValue('value')
const { result } = renderHook(() => usePoll(fetcher))
await waitFor(() => {
expect(result.current.data).toBe('value')
})
expect(result.current.error).toBeNull()
})
it('surfaces an Error message', async () => {
const fetcher = vi.fn().mockRejectedValue(new Error('boom'))
const { result } = renderHook(() => usePoll(fetcher))
await waitFor(() => {
expect(result.current.error).toBe('boom')
})
})
it('stringifies a non-Error rejection instead of rendering nothing', async () => {
const fetcher = vi.fn().mockRejectedValue('plain string')
const { result } = renderHook(() => usePoll(fetcher))
await waitFor(() => {
expect(result.current.error).toBe('plain string')
})
})
it('clears a previous error once a load succeeds again', async () => {
const fetcher = vi
.fn()
.mockRejectedValueOnce(new Error('boom'))
.mockResolvedValue('ok')
const { result, rerender } = renderHook(
({ interval }: { interval: number }) => usePoll(fetcher, interval),
{ initialProps: { interval: 100000 } },
)
await waitFor(() => {
expect(result.current.error).toBe('boom')
})
rerender({ interval: 200000 })
await waitFor(() => {
expect(result.current.data).toBe('ok')
})
expect(result.current.error).toBeNull()
})
it('polls again on the interval', async () => {
vi.useFakeTimers()
const fetcher = vi.fn().mockResolvedValue('value')
renderHook(() => usePoll(fetcher, 1000))
expect(fetcher).toHaveBeenCalledTimes(1)
await vi.advanceTimersByTimeAsync(2000)
expect(fetcher).toHaveBeenCalledTimes(3)
})
it('stops updating after unmount', async () => {
const fetcher = vi.fn().mockResolvedValue('value')
const { result, unmount } = renderHook(() => usePoll(fetcher))
unmount()
await Promise.resolve()
expect(result.current.data).toBeNull()
})
it('ignores a rejection that lands after unmount', async () => {
// The cancelled guard in the catch path: without it React warns about a
// state update on an unmounted component, and a stale error would stick.
let reject: (reason: Error) => void = () => undefined
const fetcher = vi.fn(
() =>
new Promise<string>((_resolve, rej) => {
reject = rej
}),
)
const { result, unmount } = renderHook(() => usePoll(fetcher))
unmount()
reject(new Error('late failure'))
await Promise.resolve()
expect(result.current.error).toBeNull()
})
it('exposes a sane default interval', () => {
expect(POLL_MS).toBeGreaterThan(0)
})
})