Testing Guide¶
There is no automated test suite — this UI is a manual test harness for the backend. Use the scenarios below to verify each demonstrated behavior.
Prerequisites¶
poc-backendand Redis running locally:docker compose up(from the repository root)- UI running locally:
npm install && npm run dev→ http://localhost:3000
Scenario checklist¶
1. Serving region info¶
- Page loads and the Serving region card shows
region,cluster,pod,version,redis, andstartedAtpopulated. - Wait ~5s: values refresh automatically without a reload.
-
redisfield shows the backend's Redis connection status.
2. Redis key/value round-trip¶
- Enter
key = foo,value = bar, click Set —fooappears in the list. - Repeat with a second key; both persist across a page reload.
- Click delete next to
foo— it disappears from the list. - Submitting with an empty key does nothing (guard in
save()).
3. Multi-region / shared state (requires ≥2 deployments)¶
- Open the UI served by region A, set a key.
- Open the UI served by region B (or reload while traffic shifts) — the same key is listed, proving shared Redis state.
- The region/cluster/pod fields differ between the two views.
4. Backend failure handling¶
- Stop the backend (
docker compose stopor kill the container). - Within ~5s the UI shows a red
backend unreachablebanner. - Restart the backend — the banner clears and data reappears.
5. Container image behavior¶
docker build -t poc-ui .
docker run -p 8080:8080 -e BACKEND_URL=http://host.docker.internal:8080 poc-ui
- http://localhost:8080 serves the UI.
-
curl localhost:8080/healthzreturnsok. -
/api/inforesponds through the nginx proxy. - Changing
BACKEND_URLrepoints the proxy without rebuilding the image.
6. Build sanity¶
-
npm run buildcompletes;dist/is produced. -
npm run previewserves the production build locally.