ATS-PFM-ELG-018 Manage personal responses to attention items: Capability Test Specification
Markdown Design / Platform / Eligibility, Responsibilities and Attention / Personal Attention / Capability Test Specification Show evidence (sources, provenance, origins, pinned commits)Coverage Rule gap: FND-PFM-ELG-070 Transition gap: FND-PFM-ELG-070 Validation covered Permission gap: FND-PFM-ELG-070 Edge gap: FND-PFM-ELG-070 Failure gap: FND-PFM-ELG-070 Boundary covered Concurrency gap: FND-PFM-ELG-070 Invariant gap: FND-PFM-ELG-070 Interaction covered Test Scenarios 11 scenarios proving CAP-PFM-ELG-018 ; 7 bound to an existing test.
01 Reject actions on final occurrences validation unit negative test
Proves BR-CAP-PFM-ELG-018-01 INV-DOM-PFM-ELG-005-04 Preconditions Resolved and expired occurrences exist. Steps Attempt every personal response. Expected Every response fails because the occurrence is closed. Data No fixtures beyond the described setup. Bound to Source services-platform:modules/attention/tests/unit/rules.spec.js #refuses every action on an item that is no longer open 04 Check postponement bounds boundary unit negative test
Proves BR-CAP-PFM-ELG-018-04 Preconditions A required kind allows one snooze and an advisory is present. Steps Try repeated or excessive required snoozes, advisory snoozes of 90 and 91 days and a past end. Expected Required excesses, 91 days and past ends fail while a 90-day advisory snooze passes. Data No fixtures beyond the described setup. Bound to Source services-platform:modules/attention/tests/e2e/attention.e2e.spec.js #refuses a second snooze of a required item allowed once, with 409 snooze_limit 11 Expose competing first personal responses concurrency api negative proposed
Proves INV-DOM-PFM-ELG-005-08 BR-CAP-PFM-ELG-018-07 Preconditions An open occurrence reaches one person and has no personal response row. Steps Pause two first actions after the audience read, release their insertions together and inspect outcomes and state. Expected A first-insert collision can refuse one request rather than transparently retrying; the stored state and accepted audit remain inspectable. Data Run-owned fixtures, separate caller contexts and a controlled clock where required. Source services-platform:modules/attention/services/persistence/states.ts :applyStateAction ← Previous Capability Test Specification ATS-PFM-ELG-017 · Deliver relevant attention with a reason: Capability Test Specification Next Capability Test Specification → ATS-PFM-ELG-019 · Escalate overdue attention and plan reminders: Capability Test Specification