sjat/boma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

ADR-008: tests run on ubongo; stub Level 4 service-UI acceptance

Browse source
This commit is contained in:
sjat 2026-06-05 09:42:01 +02:00
parent 07bc1c83f0
commit 66064be7b2
1 changed files with 10 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/decisions/008-testing.md
View file

@ -12,7 +12,7 @@ This document records the testing strategy, what each level covers, and — crit
### Level 1 — Molecule (per role, always required) ### Level 1 — Molecule (per role, always required)
Runs in Docker on the control node or in CI. Fast (~5 min per role). Runs in Docker on the control node (`ubongo`) or in CI. Fast (~5 min per role).
**What happens during `molecule test`:** **What happens during `molecule test`:**
1. `create` — start the test container 1. `create` — start the test container
@ -53,6 +53,15 @@ Once `askari` is operational: scripted checks from outside the network confirmin
that public-facing services respond correctly. Catches firewall and reverse proxy that public-facing services respond correctly. Catches firewall and reverse proxy
configuration issues invisible to Ansible check mode. configuration issues invisible to Ansible check mode.
### Level 4 — Service-UI acceptance (planned, not built)
Claude drives a headless browser from `ubongo` against a *deployed* service: loads
the rendered UI, creates test users, exercises features, and hands the operator a
manual test script for the rest. Catches application-level regressions that no lower
level sees. The harness (Playwright/headless-Chromium, screenshot-back-to-Claude) is
a **separate spec**; `ubongo` is sized for it (ADR-015). Status: designed, not built
(STATUS.md).
--- ---
## Molecule test image ## Molecule test image