ATS-CMT-MTG-008Approve minutes and preserve later corrections: Acceptance Test Set
MarkdownApprove minutes and preserve later corrections: Acceptance Test Set
Coverage
Test Scenarios
12 scenarios proving CAP-CMT-MTG-008; 10 bound to an existing test.
01 Approval rejects draft and already approved textapinegativetest
- Proves
BR-CAP-CMT-MTG-008-01 - Preconditions
- Fixtures include draft and approved minutes.
- Steps
- Attempt approval for each; circulate the draft and then complete its valid approval.
- Expected
- Invalid lifecycle requests fail and the circulated revision can be approved.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Bound to
- Source
- react-console:acceptance/committees/playwright/journeys/decisions/CMT-ACC-0342.spec.ts#CMT-ACC-0342
02 Rules select decision-based or direct actor approvalapitest
- Proves
BR-CAP-CMT-MTG-008-02 - Preconditions
- One committee requires a vote and another does not.
- Steps
- Approve each committee’s circulated minutes through the authorised API.
- Expected
- The first has a carried approval decision; the second has no decision and records the caller as approver.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Bound to
- Source
- services-committees:modules/decisions/tests/integration/services/consequences.integration.spec.ts#approves them by a carried decision of kind approval, taken by voice at the next meeting
04 Approval retains protected contentapinegativetest
- Proves
BR-CAP-CMT-MTG-008-04 - Preconditions
- Minutes have been approved with a known circulated fingerprint.
- Steps
- Read them later and attempt to replace their text or reopen their status.
- Expected
- The fingerprint remains unchanged and ordinary rewriting and reopening fail.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Bound to
- Source
- services-committees:modules/decisions/tests/integration/services/consequences.integration.spec.ts#keeps the circulated text’s hash on approval
05 A correction becomes a separately approved revisionapitest
- Proves
BR-CAP-CMT-MTG-008-05 - Preconditions
- A meeting has approved minutes.
- Steps
- Start a correction, save its text, circulate it and approve it.
- Expected
- The correction has the next revision number and links to the original, which then becomes amended.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Bound to
- Source
- services-committees:modules/decisions/tests/integration/services/consequences.integration.spec.ts#starts a correction as the next revision, superseding them
06 Approval checks its dedicated permissionapinegativetest
- Proves
BR-CAP-CMT-MTG-008-06 - Preconditions
- A staff caller has meeting-management permission but lacks minutes-management permission.
- Steps
- Request approval of circulated minutes.
- Expected
- The API returns forbidden.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Bound to
- Source
- services-committees:modules/decisions/tests/e2e/decisions.e2e.spec.ts#refuses minutes approval to a caller without committees.minutes.manage, 403
07 Approval produces its event and participant submissionsapitest
- Proves
BR-CAP-CMT-MTG-008-07 - Preconditions
- A meeting’s circulated minutes are ready for approval.
- Steps
- Complete approval with a recording notifier and event publisher.
- Expected
- Each participant has an approval submission and an approval event is recorded.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Bound to
- Source
- services-committees:modules/decisions/tests/integration/services/consequences.integration.spec.ts#tells the meeting’s participants they were approved
08 Approval is deferred beyond the meetings-only releaseapiproposed
- Proves
BR-CAP-CMT-MTG-008-08 - Preconditions
- Only the meetings milestone is delivered.
- Steps
- Inspect availability and attempt minutes approval.
- Expected
- Approval remains unavailable until the decisions milestone is delivered.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Source
- services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D7
09 The approval journey retains the circulated fingerprintapitest
- Proves
AS-JNY-CMT-MTG-002-01 - Preconditions
- The journey has approved the reviewed revision.
- Steps
- Compare its fingerprint with circulation and attempt an ordinary content rewrite.
- Expected
- The fingerprint is retained and protected content cannot be rewritten.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Bound to
- Source
- services-committees:modules/decisions/tests/integration/services/consequences.integration.spec.ts#refuses any change of approved minutes
12 Version conflicts and omitted approval tallies are explicitapinegativeproposed
- Proves
BR-CAP-CMT-MTG-008-10 - Preconditions
- Circulated minutes have a current saved version and the committee approves by a tally method.
- Steps
- Attempt approval and correction with stale versions; submit a valid tally-based approval with no tally.
- Expected
- Stale requests fail without changing minutes; omitted counts produce a declared-carried tally.
- Data
- An isolated workspace with circulated minutes, rule profiles, meeting quorum and permission-bearing and restricted callers.
- Source
- services-committees:modules/decisions/services/minutes/minutes-approval.ts:approveMeetingMinutes