From 66064be7b2b91771c6d30273d94dfc3cdbc0722b Mon Sep 17 00:00:00 2001 From: sjat Date: Fri, 5 Jun 2026 09:42:01 +0200 Subject: [PATCH] ADR-008: tests run on ubongo; stub Level 4 service-UI acceptance --- docs/decisions/008-testing.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/decisions/008-testing.md b/docs/decisions/008-testing.md index 005de2b..aa45d3d 100644 --- a/docs/decisions/008-testing.md +++ b/docs/decisions/008-testing.md @@ -12,7 +12,7 @@ This document records the testing strategy, what each level covers, and — crit ### 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`:** 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 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