ATS-CMT-MTG-002Maintain a committee’s recurring meeting schedule: Acceptance Test Set
MarkdownMaintain a committee’s recurring meeting schedule: Acceptance Test Set
Coverage
Test Scenarios
9 scenarios proving CAP-CMT-MTG-002; 6 bound to an existing test.
01 Unsupported recurrence is explained and rejectedunitnegativetest
- Proves
BR-CAP-CMT-MTG-002-01 - Preconditions
- The recurrence parser and series endpoint are available.
- Steps
- Submit annual recurrence, missing start hours, set-position rules, ordinal-free monthly weekdays, and a count combined with an end; expand valid schedules.
- Expected
- Invalid schedules return a reason; supported schedules produce the specified dates.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Bound to
- Source
- services-committees:modules/meetings/tests/unit/services/recurrence-rule.spec.ts#refuses a yearly rule
02 Duration and date boundaries are checkedapinegativetest
- Proves
BR-CAP-CMT-MTG-002-02 - Preconditions
- An active committee is available.
- Steps
- Create series lasting zero, one, 1,440 and 1,441 minutes; submit an end before the start.
- Expected
- One and 1,440 minutes are accepted; out-of-range durations and reversed dates are rejected.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Bound to
- Source
- react-console:acceptance/committees/playwright/journeys/meetings/CMT-ACC-0218.spec.ts#CMT-ACC-0218
03 Generating a monthly calendar twice adds no duplicateapitest
- Proves
BR-CAP-CMT-MTG-002-03 - Preconditions
- A board has dated appointments.
- Steps
- Save a second-Tuesday schedule and generate its occurrences a second time.
- Expected
- The first generation creates the expected window; the repeat creates no new occurrence.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Bound to
- Source
- services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#creates one meeting per occurrence of the window, on the second Tuesdays
04 A named workspace’s daily run isolates work and reports failuresapitest
- Proves
BR-CAP-CMT-MTG-002-04 - Preconditions
- Two workspaces contain series; one series belongs to a committee dissolved after setup.
- Steps
- Invoke the daily handler for the first workspace.
- Expected
- Eligible series are generated, the dissolved committee’s series is reported as failed, and the second workspace receives no meetings.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Bound to
- Source
- services-committees:modules/meetings/tests/integration/services/meetings-jobs-tenant.integration.spec.ts#materialises both of the named tenant’s series, each over the same window
05 A series edit preserves completed occurrencesapitest
- Proves
BR-CAP-CMT-MTG-002-05 - Preconditions
- A series contains future meetings and held and cancelled occurrences.
- Steps
- Move the series start time one hour earlier.
- Expected
- Future draft and scheduled occurrences change time; held and cancelled meetings retain their details.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Bound to
- Source
- services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#rewrites the future unheld occurrences to the new time
06 Calling follows the committee’s lead timeapiproposed
- Proves
BR-CAP-CMT-MTG-002-06 - Preconditions
- The committee uses the initial thirty-day lead time.
- Steps
- Create a monthly schedule, then run the daily process before and at the calling boundary.
- Expected
- Distant occurrences remain drafts; at the boundary each becomes scheduled and the calling side effects permitted by policy occur.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Source
- services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D3
07 Resuming restores eligible datesapiproposed
- Proves
BR-CAP-CMT-MTG-002-07 - Preconditions
- An active monthly schedule has future occurrences.
- Steps
- Pause the series, then resume it.
- Expected
- Pausing cancels future occurrences; resuming restores the remaining eligible dates.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Source
- services-committees:docs/milestones/plans/CMTE-M3-plan.md#D12
08 An individually moved meeting survives a series editapiproposed
- Proves
BR-CAP-CMT-MTG-002-08 - Preconditions
- Staff moved the March occurrence from Tuesday to Wednesday.
- Steps
- Change the recurring start hour.
- Expected
- The March meeting retains its individually chosen date and time.
- Data
- A disposable workspace containing a committee, appointments and a controlled current date.
- Source
- services-committees:docs/milestones/plans/CMTE-M3-plan.md#D12