T12.6: wave 12 verification record, browser probe, BL-060
- tests/bulk_users_ui_check.py (new): selection, keyboard Space on a row box, toolbar role change, super-user CSV with good and bad lines, add-to-project with a role, typed DELETE, all end to end against a real server; 390px bar layout; writes after-screenshots to docs/reference/baseline/wave-12/. Needs a browser: to be run on Matt's machine. - tests/cdp.py: --do-not-de-elevate and the rc=0 grace, the same change as wave 16 T16.4 (identical content, merges cleanly), so the probes start from an elevated shell on this branch too. - Verification record in wave-12.md: bulk_users_check 61/61 (main 7/18), single-user routes identical before/after on 16 calls, DOM harness 48/48, jsdom against a real server 13/13, smoke 27/27, seed_demo OK. Server-checkable done-when boxes ticked; the browser, screenshot and full-suite boxes stay open until run on Edge. - BL-060 logged: a super user's refusal reason promises a project access change neither the dialog nor the bulk route allows. Needs Nick; not fixed here (scope). - file-map.md: wave 12's two new checks.
This commit is contained in:
@@ -316,6 +316,17 @@ python tests/critical_reopen_check.py # BL-021 - on-hold mail reaches PM + CM
|
||||
python tests/console_dialogs_check.py # BL-024 - consoles/launcher: 21 natives -> 0 17 checks
|
||||
```
|
||||
|
||||
Wave 12 (CR-020, bulk user editing) adds these:
|
||||
|
||||
```bash
|
||||
python tests/bulk_users_check.py # CR-020 - bulk routes, guards, audit, CSV; NO browser 61 checks
|
||||
python tests/bulk_users_ui_check.py # CR-020 - selection, toolbar, CSV, typed delete at 1440/390px
|
||||
```
|
||||
|
||||
`console_dialogs_check.py` gained section 4 (the bulk delete prompt). `tests/cdp.py`
|
||||
passes `--do-not-de-elevate` on Windows so the probes start from an Administrator
|
||||
shell (same change as wave 16, T16.4).
|
||||
|
||||
**Three probes were re-pointed at `T7.1`.** `sections_check.py` 5b drove the live
|
||||
cross-frame toggle hand-off, which no longer exists; it now pins the surviving path and
|
||||
the fact that an UNSAVED toggle correctly does not travel - a behaviour change, recorded
|
||||
|
||||
Reference in New Issue
Block a user