Work from personal and shared task views: Acceptance Test Set

Coverage

Bound scenarios identify existing assertions; unbound scenarios remain proposed proof. Static inspection does not establish a passing execution.

Show evidence (sources, provenance, origins, pinned commits)

4 scenarios proving CAP-CRM-ACT-014; 3 bound to an existing test.

01 Align general task views with the registered datasetunittest

Proves: BR-CAP-CRM-ACT-014-01
Preconditions: The shipped recipe and console definition are available.
Steps: Compare their fields, criteria and ordering.
Expected: The definition uses supported dataset fields and aligns with its recipe.
Data: Each run creates and isolates the records it needs.
Bound to: react-console:components/console/tasks/__tests__/tasks-definition.test.tsx#agrees with the recipe it is anchored to
react-console:components/console/tasks/__tests__/tasks-definition.test.tsx#names only fields this dataset answers, with operators those fields accept
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0714.spec.ts#CRM-ACC-0714
services-crm:modules/tasks/tests/unit/metadata/tasks-object.spec.js#describes the assignee as a reference to Users
Source: react-console:components/console/tasks/__tests__/tasks-definition.test.tsx#agrees with the recipe it is anchored to

02 Gate task creation and preserve queue contextunitnegativetest

Proves: BR-CAP-CRM-ACT-014-05
Preconditions: Read-only and creation-capable users can render the header.
Steps: Open the task header and initiate creation from a queue view.
Expected: Only creation-capable users receive the action and queue context is preselected.
Data: Each run creates and isolates the records it needs.
Bound to: react-console:components/tasks/__tests__/tasks-page.test.tsx#offers Create Task only to someone who may create a task
react-console:components/tasks/__tests__/tasks-page.test.tsx#pre-selects the queue the view stands for
Source: react-console:components/tasks/__tests__/tasks-page.test.tsx#offers Create Task only to someone who may create a task

03 Keep closed and unauthorized drawers read-onlyunitnegativetest

Proves: BR-CAP-CRM-ACT-014-06
Preconditions: Readers and editors open both open and closed tasks.
Steps: Inspect fields and menu actions for each combination.
Expected: Editing and actions follow the corresponding status and permission limits.
Data: Each run creates and isolates the records it needs.
Bound to: react-console:components/tasks/__tests__/task-detail-sheet.test.tsx#offers only what each permission allows
react-console:components/tasks/__tests__/task-detail-sheet.test.tsx#disables every field, the complete toggle and Assign to Me
react-console:components/tasks/__tests__/task-detail-sheet.test.tsx#offers no task menu at all
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0716.spec.ts#CRM-ACC-0716
Source: react-console:components/tasks/__tests__/task-detail-sheet.test.tsx#offers only what each permission allows

04 Provide offered-work discovery as a proposed console outcomebrowserproposed

Proves: BR-CAP-CRM-ACT-014-09
Preconditions: A task is offered to a role held by the user.
Steps: Open the Tasks screen.
Expected: The proposed view exposes relevant role offers; implementation remains outstanding.
Data: Each run creates and isolates the records it needs.
Source: FND-CRM-ACT-010