console fill apple-app-privacy: set up each data type from the real page ('Set Up <type>' is a plain text, clicked by its exact text in the Data Types section), fill its dialog step by step, dump and pause on an unknown step; '?' and Publish never clicked
This commit is contained in:
parent
3aedf9e137
commit
e0bef82b06
7 changed files with 500 additions and 28 deletions
|
|
@ -156,6 +156,17 @@ Each entry: **symptom** → cause → what to do → what guards it now. The ful
|
|||
- **Guard:** `signInReason` in `cli/console/fill.ts` (top-level URL, the main frame's password / email-entry form, a
|
||||
visible Apple sign-in frame; no other frame counts), the sign-in watchdog dump, `tests/console-fill.test.ts`.
|
||||
|
||||
## 17. App Privacy data types listed but never set up
|
||||
- **Symptom:** after the data types were saved, `console fill apple-app-privacy` stops on the App Privacy page with
|
||||
every type showing "Set Up <type>" and nothing clicked.
|
||||
- **Cause:** the real page shows "Set Up <type>" as plain text (a `<p>` in a div with a click handler: no button, no
|
||||
link) in a box after the Data Types heading, so role-based lookups miss it.
|
||||
- **Do:** nothing by hand: storebound clicks each "Set Up <type>" by its exact text (only for types it answers, never
|
||||
the "?" help buttons or Publish) and fills that type's dialog step by step. A dialog step it does not know: it writes
|
||||
a debug dump, says `paused on "<type>"`, and goes on once the owner answered that step.
|
||||
- **Guard:** `setUpAllowed` (`cli/lib/console-forms.ts`), `setUpClick` / `setUpType` (`cli/console/fill.ts`),
|
||||
`tests/console-flow.test.ts` with `tests/fixtures/console/apple-app-privacy-setup.html`.
|
||||
|
||||
## Adding a lesson
|
||||
Every bug found in real use gets an entry in `docs/pitfalls.md` and here, and, where possible, a check or a test
|
||||
that fails without the fix (see CONTRIBUTING.md).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue