Skip to content

docs(qa): document the area-level fixtures recipe convention in the platform-checklist README #7720

Description

@huangyiirene

Blocked-by: #7716

Linkage chore from PR #7716 (#7670), filed by the devx PM per the accepted option B on that PR's open question.

Task

docs/qa/platform-checklist/README.md's "Item anatomy" documents fixtures only per-item. PR #7716 introduced an area-level fixtures block (a named provisioning recipe, e.g. qa-scratch-authz in areas/attachments-storage.json) that items opt into via fixtures.provisioning = { use, why }. Document both halves of that convention in README.md's Item anatomy so the next area that needs a shared recipe copies a documented shape instead of reverse-engineering the first one.

Deliberately deferred (option C on the same question): teaching check-platform-checklist.mjs to resolve fixtures.provisioning.use against the area's fixtures keys — revisit only if the recipe shape spreads to more areas.

Provenance

No domain:* label — routing is the triage seat's. pm:blocked omitted in favor of the Blocked-by: line + pm:queue since #7716 is expected to merge within the hour; if selection reaches this card first, the line above defers it.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions