stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 3 Releases Wiki Activity

Close scratch iteration 008 and enforce full surface audits

Browse Source
This commit is contained in:
master
2026-03-13 11:00:12 +02:00
parent fe35801cc5
commit c9a30331ce
11 changed files with 534 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/qa/feature-checks/FLOW.md
View File

@@ -229,6 +229,8 @@ A Tier 2 run is valid only if ALL of the following are true:
3. It includes user-surface interactions (HTTP requests, CLI invocations, or UI interactions), not only library test counts.
4. It verifies both positive and negative behavior paths when the feature has error semantics.
5. For rechecks, at least one new user transaction per feature is captured in the new run.
6. For UI features, the run covers the full visible user surface for that feature: every route, every page-load state, and every visible action that can be exercised in the local environment.
7. Any newly discovered manual UI flow or regression path is converted into retained Playwright coverage before the feature may be considered stably verified.
The following are forbidden and invalidate Tier 2:
- Copying a previous run directory and only editing `runId`, timestamps, or summary text.
@@ -321,10 +323,12 @@ echo $? # Verify exit code 0
**Process**:
1. Ensure the Angular app is running (`ng serve` or docker)
2. Use Playwright CLI or MCP to navigate to the feature's UI route
3. Follow E2E Test Plan steps: verify elements render, interactions work, data displays
4. If the feature fails only through transient network/runtime noise, rerun the failing UI transaction in a fresh page or fresh authenticated browser context before declaring the feature failed. Preserve both the first failure evidence and the recheck outcome.
5. Capture screenshots as evidence
6. Test accessibility (keyboard navigation, ARIA labels) if listed in E2E plan
3. Traverse the full visible UI surface for the feature: every route, every page-load state, and every visible action that can be exercised locally.
4. Follow E2E Test Plan steps: verify elements render, interactions work, and data displays with the correct state and routing.
5. If the feature fails only through transient network/runtime noise, rerun the failing UI transaction in a fresh page or fresh authenticated browser context before declaring the feature failed. Preserve both the first failure evidence and the recheck outcome.
6. Capture screenshots as evidence
7. Test accessibility (keyboard navigation, ARIA labels) if listed in E2E plan
8. If manual exploration exposes a route/action not already covered by the retained Playwright suite, add or extend a Playwright scenario before closing the verification loop so the next run replays that path automatically.
**Example for `pipeline-run-centric-view`**:
```bash