Skip to content

ATS-CMT-MTG-005Release meeting papers as a packet: Acceptance Test Set

Markdown

ATS-CMT-MTG-005

Release meeting papers as a packet: Acceptance Test Set

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CMT-MTG-005

KindAcceptance test setProduct areaCommitteesModuleMeetings, Decisions and RecruitmentRevision2

Read atservices-committees 36129c24react-console baf6dae3

Test Scenarios

8 scenarios proving CAP-CMT-MTG-005; 2 bound to an existing test.

01 Materials require a file and a valid meeting-item relationshipapinegativeproposed
Proves
BR-CAP-CMT-MTG-005-01
Preconditions
Two meetings each have agenda items.
Steps
Create one material naming the other meeting’s item and another with no file.
Expected
Neither request stores a material.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Source
services-committees:modules/meetings/services/persistence/meeting-materials.ts:addMaterial
02 File preparation refuses unsafe and foreign sourcesapinegativetest
Proves
BR-CAP-CMT-MTG-005-02
Preconditions
A meeting has valid, unsafe and foreign-workspace upload fixtures.
Steps
Attempt each file as a material and retrieve stored references.
Expected
Unsafe and foreign sources fail without records; the valid source becomes a permanent reference in the material storage area.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Bound to
services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#stores the permanent reference in the material’s own folder
services-committees:modules/meetings/tests/e2e/meetings.e2e.spec.ts#stores the material’s file through the asset pipeline, as a permanent reference
Source
services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#refuses a file of another tenant and writes nothing
03 Publication includes later additions without republishingapinegativetest
Proves
BR-CAP-CMT-MTG-005-04
Preconditions
A scheduled meeting has two prepared materials.
Steps
Publish its packet, add another material, then attempt publication again.
Expected
The original and later materials carry publication timestamps; repeated publication is refused.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Bound to
services-committees:modules/meetings/tests/unit/services/meeting-lifecycle.spec.ts#publishes the packet once, of a meeting that has not ended
Source
services-committees:modules/meetings/tests/unit/services/meeting-lifecycle.spec.ts#publishes the packet once, of a meeting that has not ended
04 Participation controls access to a released paperapinegativeproposed
Proves
BR-CAP-CMT-MTG-005-05
Preconditions
A published material is restricted to meeting participants.
Steps
Read its meeting page as a participant and as an unrelated caller.
Expected
The participant receives the material and the unrelated caller cannot read the meeting.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Source
FND-CMT-MTG-035
05 Deletion eventually retires an eligible fileapiproposed
Proves
BR-CAP-CMT-MTG-005-06
Preconditions
A material is attached to a meeting.
Steps
Delete the material, sweep asset cleanup and process the queued retirement.
Expected
The material disappears and cleanup retires its file after confirming it has no remaining live reference.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Source
FND-CMT-MTG-027
06 The interim packet accepts a link-only entryapiproposed
Proves
BR-CAP-CMT-MTG-005-07
Preconditions
A meeting is scheduled.
Steps
Add a title and web address, then publish the packet.
Expected
The link-only entry is saved and released with the other papers.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Source
services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D10
07 Packet labels and order can change independently of filesapiproposed
Proves
BR-CAP-CMT-MTG-005-08
Preconditions
A packet contains three file entries.
Steps
Rename its second entry, place it first and attempt to replace the file directly.
Expected
Label and ordering changes persist; direct file replacement is refused.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Source
services-committees:docs/milestones/plans/CMTE-M3-plan.md#D12
08 Cancelled meetings refuse new papersapinegativeproposed
Proves
BR-CAP-CMT-MTG-005-03
Preconditions
A meeting is cancelled and a valid upload is available.
Steps
Attempt to attach the upload as a meeting material.
Expected
The request returns meeting_cancelled and stores no material.
Data
A disposable workspace with two meetings, agenda items and valid, unsafe and foreign-workspace file fixtures.
Source
services-committees:modules/meetings/services/persistence/meeting-materials.ts:addMaterial

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.