ATS-CRM-ACT-006Review activity changes and their attribution: Acceptance Test Set

ATS-CRM-ACT-006

Review activity changes and their attribution: Acceptance Test Set

KindAcceptance test setProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Review activity changes and their attribution: 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)

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

01 Restrict revision accessapinegativetest

Proves: BR-CAP-CRM-ACT-006-01
Preconditions: The caller has activity read but no history permission.
Steps: Request activity history.
Expected: The request returns Forbidden.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses the history to a caller without crm.activities.history: 403
react-console:components/activities/__tests__/activities-explorer-and-history.test.ts#refuses a reader who does not hold crm.activities.history, as CRM does
Source: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses the history to a caller without crm.activities.history: 403

02 Record the full activity revision lifecycleapitest

Proves: BR-CAP-CRM-ACT-006-02 BR-CAP-CRM-ACT-006-03
Preconditions: An activity can be created, corrected and deleted.
Steps: Create the activity, change its subject, delete it and read its history.
Expected: Creation, correction and deletion yield attributed revisions ordered newest first, still readable after deletion.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#writes one revision of record type crm.activities, attributed to the caller
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#writes an update revision naming the changed subject
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#writes a deletion revision
services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#answers its history, newest first: the update and the create
Source: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#writes one revision of record type crm.activities, attributed to the caller

03 Resolve historical entry labels from current recordsapitest

Proves: BR-CAP-CRM-ACT-006-04
Preconditions: An activity links a contact renamed after creation.
Steps: Open the creation revision.
Expected: The revision separates its sections and labels the contact with its current name.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#shows the creation section by section, the linked records named as they are called
services-crm:modules/activities/tests/integration/services/history/activity-history.integration.spec.js#presents the creation’s outcome under “Outcome” by the name the type gives it
react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0702.spec.ts#CRM-ACC-0702
Source: services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#shows the creation section by section, the linked records named as they are called