Retain supporting files with an activity: 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-004; 4 bound to an existing test.

01 Reject attachment overflowapinegativetest

Proves: BR-CAP-CRM-ACT-004-01
Preconditions: An activity can accept valid managed attachments.
Steps: Submit 21 attachment entries.
Expected: The request identifies the attachment limit.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#refuses more than 20 attachments
Source: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#refuses more than 20 attachments

02 Require prepared managed file referencesapinegativetest

Proves: BR-CAP-CRM-ACT-004-02
Preconditions: A prepared upload and an unprepared address are available.
Steps: Save activities with each reference.
Expected: The prepared file becomes permanent and the unprepared reference is rejected.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#stores an uploaded file as a permanent reference of the activity, and attaches its lifecycle row
services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#refuses a file reference that did not come through the pipeline
Source: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#stores an uploaded file as a permanent reference of the activity, and attaches its lifecycle row

03 Replace only the submitted attachment listapitest

Proves: BR-CAP-CRM-ACT-004-03
Preconditions: An activity holds two attachments.
Steps: Submit a replacement list containing one unchanged file.
Expected: Only that file remains attached.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#keeps an attachment sent back unchanged, and removes one left out
Source: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#keeps an attachment sent back unchanged, and removes one left out

04 Skip file copying during create replayapitest

Proves: BR-CAP-CRM-ACT-004-06
Preconditions: A managed attachment accompanies activity creation.
Steps: Repeat the create under the same identifier.
Expected: The permanent file is reused without a second copy.
Data: Each run creates and isolates the records it needs.
Bound to: services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js#copies nothing for the retry
services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js#answers the attachment the first attempt stored
Source: services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js#copies nothing for the retry