From 4955c3ac1f7388ca51cda8c3be6a374c621aa143 Mon Sep 17 00:00:00 2001 From: russellwheatley Date: Wed, 26 Aug 2026 13:00:02 +0100 Subject: [PATCH] docs(okf): add e2e startup fail-fast markers Watchers of :test-cover were waiting out launchApp 180s and Detox retries. Name the healthy launch strings and the known fail strings so a failed launch stops instead of looking like a mid-suite stall. --- okf-bundle/testing/running-e2e.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/okf-bundle/testing/running-e2e.md b/okf-bundle/testing/running-e2e.md index 6c7db6c203..02a3a1783d 100644 --- a/okf-bundle/testing/running-e2e.md +++ b/okf-bundle/testing/running-e2e.md @@ -173,6 +173,7 @@ rg 'Tests Complete' /tmp/rnfb-e2e-.log | tail -1 # optional, 7. **Waiting on output:** during the first ~60s, `notify_on_output` / AwaitShell `pattern` **must** be the [startup-fail notify pattern](#startup-fail-fast-poll) (`E2E_STARTUP_FAILFAST_NOTIFY_PATTERN` in [`scripts/e2e/lib/e2e-startup-failfast.sh`](../../scripts/e2e/lib/e2e-startup-failfast.sh) — hard infra only, not `currentStatus` / status-query timeout). After a healthy launch, never pattern bare `passing` or bare `APP_STATUS` — use an anchored pattern such as `^\s*\d+ (passing|failing)` or `jet-coverage.*merged .* before NYC`. Prefer the Shell tool's own exit code when it returns normally after launch is healthy. + ### Startup fail-fast poll @@ -195,6 +196,11 @@ After starting `:test-cover` teed to a **unique** path (`/tmp/rnfb-e2e-