End-to-end suite report — staging
AI-generated content
This document was generated by an AI assistant. Verify accuracy before relying on the details.
Generated
pnpm report:e2e regenerates this page. Do not edit it by hand — the next run overwrites it. It does not run the suite: the inventory comes from playwright test --list, which executes nothing, and the figures come from the index and the defect list. Last run: 2026-09-16.
What the staging end-to-end suite contains, what it has proven about the deployed Angular application, and what it found while doing so. How to run it is in the suite's page.
At a glance
| Tests | 642 in 128 files |
With PW_DESIRED=1 | 671 in 148 files |
| Capabilities indexed | 249 |
| Verified end to end | 157 (63 %) |
| Confirmed defects | 21 |
Capability coverage
The verdict vocabulary is closed to five values; a sixth invented in passing is rejected by apps/ui/test/e2e-feature-index.test.mjs.
| verdict | meaning | n | share |
|---|---|---|---|
staging: yes | covered end to end | 157 | 63 % |
staging: partial | partly driven, and the row says which part | 36 | 14 % |
characterised as unreachable | no user path reaches it | 23 | 9 % |
characterised as broken | reached, and the application failed | 19 | 8 % |
staging: none | not covered, and the row says why | 14 | 6 % |
The rows marked unreachable or broken are a result, not a backlog: finding them is what the exercise was for.
The suite, by area
| area | spec files | tests |
|---|---|---|
| transverse | 31 | 171 |
| contracts | 24 | 119 |
| parts | 19 | 102 |
| accounting | 24 | 95 |
| persons | 14 | 79 |
| tickets | 12 | 62 |
| accounting (desired) | 7 | 12 |
| admin | 2 | 8 |
| tickets (desired) | 4 | 6 |
| grr | 1 | 5 |
| contracts (desired) | 4 | 4 |
| parts (desired) | 3 | 4 |
| auth (desired) | 1 | 2 |
| setup | 1 | 1 |
| persons (desired) | 1 | 1 |
Areas suffixed (desired) hold the specs that describe a fix rather than the current behaviour. They run only under PW_DESIRED=1 and are red on purpose until the defect is fixed.
Defects found
| severity | n |
|---|---|
| capacité bloquée | 6 |
| à qualifier | 5 |
| perte de données | 3 |
| écriture fausse silencieuse | 3 |
| chiffre faux affiché | 1 |
| configuration serveur | 1 |
| message trompeur | 1 |
| écran factice | 1 |
Ordered by what the user loses, with the full list and the evidence in apps/ui/e2e/staging/TO-FIX.md. Each defect has two specs: one that records it and is green today, one that specifies the fix and is red.