Configure activity types and the details they collect: Acceptance Test Set
Coverage
Bound scenarios identify existing assertions; unbound scenarios remain proposed proof. Static inspection does not establish a passing execution.
9 scenarios proving CAP-CRM-ACT-008; 9 bound to an existing test.
01 Reject type maintenance by readersapinegativetestBR-CAP-CRM-ACT-008-01 02 Derive valid type identifiers and reserve reorderapinegativetestBR-CAP-CRM-ACT-008-02 03 Reject invalid type names and descriptionsapinegativetestBR-CAP-CRM-ACT-008-03 04 Validate field-mode and default configuration limitsapinegativetestBR-CAP-CRM-ACT-008-04 BR-CAP-CRM-ACT-008-05 05 Apply outcome-list replacement semanticsapinegativetestBR-CAP-CRM-ACT-008-06 06 Retain types and outcomes referenced by activitiesapinegativetestBR-CAP-CRM-ACT-008-07 07 Retire a type while preserving prior activitiesbrowsertestBR-CAP-CRM-ACT-008-08 08 Reorder types atomicallyapinegativetestBR-CAP-CRM-ACT-008-09 09 Reject stale type replacementapinegativetestBR-CAP-CRM-ACT-008-11