Rhythm 2.0 Specifications

Appearance

ATS-CRM-ACT-015Route overdue work to the people responsible for it: Acceptance Test Set

Markdown

ATS-CRM-ACT-015

Route overdue work to the people responsible for it: Acceptance Test Set

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-ACT-015

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Route overdue work to the people responsible for it: Acceptance Test Set ​

Coverage ​

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

RuleProof Scenario Or Gap
BR-CAP-CRM-ACT-015-01ATS-CRM-ACT-015-01
BR-CAP-CRM-ACT-015-02ATS-CRM-ACT-015-02
BR-CAP-CRM-ACT-015-03ATS-CRM-ACT-015-03
BR-CAP-CRM-ACT-015-04ATS-CRM-ACT-015-04
BR-CAP-CRM-ACT-015-05ATS-CRM-ACT-015-05
BR-CAP-CRM-ACT-015-06no scenario: FND-CRM-ACT-028
BR-CAP-CRM-ACT-015-08ATS-CRM-ACT-015-06

Test Scenarios

6 scenarios proving CAP-CRM-ACT-015; 6 bound to an existing test.

01 Begin overdue attention after the due dayapinegativetest
Proves
BR-CAP-CRM-ACT-015-01
Preconditions
Tasks are due yesterday and today with publishing enabled.
Steps
Create both and inspect their emitted items.
Expected
Only yesterday’s work qualifies and its attention due instant is the end of that day.
Data
Each run creates and isolates the records it needs.
Bound to
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
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes the overdue task as it is created, addressed to its assignee, due at the end of its day in the tenant’s zone
Source
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
02 Select the holder or shared audienceapinegativetest
Proves
BR-CAP-CRM-ACT-015-02
Preconditions
Overdue fixtures are held, unassigned in a queue and unassigned outside queues.
Steps
Publish each item.
Expected
Audience selection matches holder, queue responsibility or administrators.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes the overdue task as it is created, addressed to its assignee, due at the end of its day in the tenant’s zone
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#addresses a queued task nobody holds to the task queue responsibility at its queue
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#addresses a task nobody holds, in no queue, to the tenant administrators
Source
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes the overdue task as it is created, addressed to its assignee, due at the end of its day in the tenant’s zone
03 Update attention when assignment changesapitest
Proves
BR-CAP-CRM-ACT-015-03
Preconditions
An overdue task belongs to a user.
Steps
Reassign it to another user.
Expected
Its attention audience changes with the task write.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#moves the item to the new holder when an overdue task is assigned, in the same generation
Source
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#moves the item to the new holder when an overdue task is assigned, in the same generation
04 Resolve attention with the task’s outcomeapitest
Proves
BR-CAP-CRM-ACT-015-04
Preconditions
Separate overdue tasks can close, move their date or be deleted.
Steps
Complete, cancel, reschedule and delete them.
Expected
Resolution records the corresponding outcome for each item.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#resolves the item rescheduled when the overdue task is given a later due date
Source
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#resolves the item completed when the overdue task is completed
05 Catch overdue work through the daily passapitest
Proves
BR-CAP-CRM-ACT-015-05
Preconditions
An overdue task lacks an item and another item is stale.
Steps
Execute the sweep.
Expected
The overdue task is published and the stale item is resolved.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#resolves the item of the task that is no longer overdue, which the pass did not republish
Source
services-crm:modules/tasks/tests/integration/services/persistence/task-attention-items.integration.spec.js#publishes the overdue task no write had published, with no contact
06 Keep publishing and sweeping silent when disabledunittest
Proves
BR-CAP-CRM-ACT-015-08
Preconditions
Attention execution uses the disabled switch.
Steps
Write overdue work and invoke its sweep.
Expected
The integration performs no attention reads or sends.
Data
Each run creates and isolates the records it needs.
Bound to
services-crm:tests/unit/attention-switch.spec.ts#publishes and resolves without one statement
services-crm:tests/unit/attention-switch.spec.ts#answers a sweep skipped, reading nothing
Source
services-crm:docs/attention.md#3. The switch

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