---
id: TST-CRM-ACT-007
title: Activity persistence and related writes
kind: integration
product_area: crm
module: activities-tasks
revision: 1
status: draft
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
repository: services-crm
files:
- modules/activities/tests/integration/services/persistence/activities.integration.spec.js
implements:
- ATS-CRM-ACT-001-01
- ATS-CRM-ACT-001-02
- ATS-CRM-ACT-001-04
- ATS-CRM-ACT-001-05
- ATS-CRM-ACT-001-06
- ATS-CRM-ACT-001-07
- ATS-CRM-ACT-001-08
- ATS-CRM-ACT-001-09
- ATS-CRM-ACT-001-10
- ATS-CRM-ACT-001-12
- ATS-CRM-ACT-002-03
- ATS-CRM-ACT-002-05
- ATS-CRM-ACT-003-01
- ATS-CRM-ACT-003-04
- ATS-CRM-ACT-003-05
- ATS-CRM-ACT-003-06
- ATS-CRM-ACT-003-07
- ATS-CRM-ACT-004-01
- ATS-CRM-ACT-004-02
- ATS-CRM-ACT-004-03
- ATS-CRM-ACT-006-02
- ATS-CRM-ACT-008-07
- ATS-CRM-ACT-018-01
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: Local test database fixtures and suite-owned records.
evidence:
- services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js
- Static inspection only; no runtime result is imported.
- Dependencies and doubles are inspected in the pinned suite setup and imports.
assertion_evidence:
  provenance: test
  source: services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js
---

# Activity persistence and related writes

## Verification Boundary

This suite checks module reads, writes or presentation against persisted fixtures.

## What This Suite Proves

Persistence assertions check activity defaults, field requirements, linked records, atomic follow-ups, attributed revisions, version conflicts and managed file-reference handling.

The registered scenario bindings identify the assertion contributions this executable supplies. A compound scenario can require several suites.

## What It Does Not Prove

It does not establish deployed Lambda transport, live Platform policy or end-user browser behavior.

## Real Dependencies and Test Doubles

The actual persistence or presentation functions execute against the migrated PostgreSQL database and fixture execution contexts. File handling retains real managed-reference persistence while object storage uses an in-memory stand-in.

## Must Not Be Doubled

The database queries, constraints, version checks, workspace policies and transaction boundaries under assertion remain real.