ATS-CRM-ACT-019Apply workspace access and maintenance permissions: Acceptance Test Set
MarkdownTest Scenarios
6 scenarios proving CAP-CRM-ACT-019; 6 bound to an existing test.
03 Apply activity permissions to each operationapinegativetest
- Proves
BR-CAP-CRM-ACT-019-04 - Preconditions
- Callers have read-only, user and missing-read authority.
- Steps
- Exercise activity creation, reads, edits and deletion.
- Expected
- Each operation requires its declared activity permission.
- Data
- Each run creates and isolates the records it needs.
- Bound to
- Source
- services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses a create to a caller who may only read activities: 403
04 Permit task reads without granting task changesapinegativetest
- Proves
BR-CAP-CRM-ACT-019-05 - Preconditions
- A caller holds task read only.
- Steps
- Read a task, edit it and claim it.
- Expected
- Reading succeeds and mutation requests are forbidden.
- Data
- Each run creates and isolates the records it needs.
- Bound to
- Source
- services-crm:modules/tasks/tests/e2e/tasks.e2e.spec.js#lets a caller who may only read tasks read one
05 Reserve configuration maintenance for administratorsapinegativetest
- Proves
BR-CAP-CRM-ACT-019-06 - Preconditions
- Callers may inspect activity and task configuration only.
- Steps
- Create an activity type and reorder task types.
- Expected
- Both maintenance requests are forbidden.
- Data
- Each run creates and isolates the records it needs.
- Bound to
- Source
- services-crm:modules/activities/tests/e2e/activities.e2e.spec.js#refuses a type’s create to a caller who may only read types: 403