Rhythm 2.0 Specifications

Appearance

ATS-CRM-ACT-014Work from personal and shared task views: Capability Test Specification

Markdown

ATS-CRM-ACT-014

Work from personal and shared task views: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-ACT-014

Design

Executed by
TST-CRM-ACT-031, TST-CRM-ACT-058, TST-CRM-ACT-060, TST-CRM-ACT-073, TST-CRM-ACT-075, TST-CRM-ACT-078

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision3

Read atservices-crm a8d1364freact-console baf6dae3rhythm-v2-docs 18a49edf

Work from personal and shared task views: Capability Test Specification ​

Coverage ​

Category coverage counts specified proof. Unbound cases remain proposed; registered assertions do not establish a passing run.

RuleProof Scenario Or Finding
BR-CAP-CRM-ACT-014-01ATS-CRM-ACT-014-01, ATS-CRM-ACT-014-05
BR-CAP-CRM-ACT-014-04FND-CRM-ACT-060
BR-CAP-CRM-ACT-014-05ATS-CRM-ACT-014-02
BR-CAP-CRM-ACT-014-06ATS-CRM-ACT-014-03
BR-CAP-CRM-ACT-014-09ATS-CRM-ACT-014-04, ATS-CRM-ACT-014-05

A user has personal overdue work and an unqueued role offer. Read the personal and overdue query views and the offered-list API for that user; inspect available console views.

The interaction scenario names the capabilities and rules it exercises. The coverage finding retains incomplete permission combinations and failure variants.

Coverage

  • Rule covered
  • Transition gap: FND-CRM-ACT-060
  • Validation gap: FND-CRM-ACT-060
  • Permission covered
  • Edge gap: FND-CRM-ACT-060
  • Failure gap: FND-CRM-ACT-060
  • Boundary gap: FND-CRM-ACT-060
  • Concurrency gap: FND-CRM-ACT-060
  • Invariant gap: FND-CRM-ACT-060
  • Interaction covered

Test Scenarios

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

01 Align general task views with the registered datasetruleunittest
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#names only fields this dataset answers, with operators those fields accept
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 contextpermissionunitnegativetest
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-onlypermissionunitnegativetest
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#disables every field, the complete toggle and Assign to Me
Source
react-console:components/tasks/__tests__/task-detail-sheet.test.tsx#offers only what each permission allows
04 Inspect the role-offer console discovery boundaryinteractionbrowserproposed
Proves
BR-CAP-CRM-ACT-014-09
Preconditions
An unqueued open task is offered to a role the current user holds.
Steps
Read offered work through its API and inspect the available Tasks views.
Expected
The eligible offer appears through the separate API; no offered-to-me view exists on the Tasks screen.
Data
Each run creates and isolates the records it needs.
Source
services-crm:modules/tasks/services/persistence/tasks.ts:listOfferedTasks; react-console:components/console/tasks/definition.tsx
05 Discovery keeps overdue lists separate from role offersinteractionapiproposed
Proves
BR-CAP-CRM-ACT-014-01 BR-CAP-CRM-ACT-014-09 BR-CAP-CRM-ACT-013-07 BR-CAP-CRM-ACT-015-01
Preconditions
A user has personal overdue work and an unqueued role offer.
Steps
Read the personal and overdue query views and the offered-list API for that user; inspect available console views.
Expected
Personal work satisfies its view criteria, the offer is available through the separate API, and the console has no offered-work view.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Source
services-crm:modules/tasks/aws/api/tasks.routes.ts:tasksRoutes; FND-CRM-ACT-010; services-crm:modules/tasks/tests/integration/services/persistence/tasks.queries.integration.spec.js#answers the three tasks offered to the user’s roles, oldest first, then by id; services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes nothing for a task due today, which is not overdue until the day ends

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software