---
id: TST-CRM-ACT-013
title: Activity field requirement decisions
kind: unit
product_area: crm
module: activities-tasks
revision: 1
status: draft
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
repository: services-crm
files:
- modules/activities/tests/unit/services/activities/field-modes.spec.js
implements:
- ATS-CRM-ACT-001-05
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: Per-test process or page fixtures with reset doubles.
evidence:
- services-crm:modules/activities/tests/unit/services/activities/field-modes.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/unit/services/activities/field-modes.spec.js
---

# Activity field requirement decisions

## Verification Boundary

This suite checks deterministic module behavior with direct assertions.

## What This Suite Proves

Fixed type and status combinations check hidden fields, missing required values, completion-only requirements and hidden-attendee link 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 helper, schema, mapper or declaration under test runs with fixed inputs. These cases use no database or deployed service.

## Must Not Be Doubled

The decision, mapper, declaration or error response being asserted remains the real implementation.