ATS-MBR-STR-001 Define unit kinds and their permitted places: Acceptance Test Set
Markdown Planning / Membership / Organizational Structure, Membership Configuration and Terms / Association Hierarchy / Capability Test Specification Define unit kinds and their permitted places: Acceptance Test Set Coverage Test Scenarios 8 scenarios proving CAP-MBR-STR-001
01 Readable kind identity survives replacement api test
Proves BR-CAP-MBR-STR-001-01Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Save one kind with an explicit reference and another by name, then replace the first kind. Expected The explicit and derived references remain the saved identities. Data The FAA example records or equivalent records prepared within the isolated workspace. Bound to Source services-membership:tests/acceptance/structure/MBR-ACC-0001.acceptance.ts #MBR-ACC-0001 staff define, rename, retire and delete kinds of unit 02 Non-root kinds need a parent choice api negative proposed
Proves BR-CAP-MBR-STR-001-02Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Attempt a non-root kind with an empty parent selection. Expected Validation rejects the request and the catalogue has no added kind. Data The FAA example records or equivalent records prepared within the isolated workspace. Source services-membership:modules/structure/services/persistence/organizational-unit-types.ts :parentIdsOf 03 Parent references are known or self-referential api negative proposed
Proves BR-CAP-MBR-STR-001-03Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Compare creation with an unknown parent kind and creation allowing its own kind. Expected The unknown choice fails and the self-referential choice saves. Data The FAA example records or equivalent records prepared within the isolated workspace. Source services-membership:modules/structure/services/persistence/organizational-unit-types.ts :requireKnownTypes 04 Duplicate kind creation preserves the first record api negative proposed
Proves BR-CAP-MBR-STR-001-04Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Submit two creates using the same kind reference. Expected The second response reports a conflict and retains the first record. Data The FAA example records or equivalent records prepared within the isolated workspace. Source services-membership:modules/structure/services/persistence/organizational-unit-types.ts :createOrganizationalUnitType 05 Existing placements protect category choices api negative test
Proves BR-CAP-MBR-STR-001-05Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Remove zone parentage while the chapter category still has units under zones. Expected The response identifies the in-use placement choice and saves no replacement. Data The FAA example records or equivalent records prepared within the isolated workspace. Bound to Source services-membership:tests/acceptance/structure/MBR-ACC-0003.acceptance.ts #MBR-ACC-0003 a tree rule chapters rely on cannot be withdrawn until they move 06 Version checks precede a complete replacement api negative test
Proves BR-CAP-MBR-STR-001-06Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Submit a stale kind replacement, then a current replacement without plural name or display order. Expected The stale write fails; the accepted replacement clears the plural and restores zero ordering. Data The FAA example records or equivalent records prepared within the isolated workspace. Bound to Source services-membership:tests/acceptance/structure/MBR-ACC-0001.acceptance.ts #MBR-ACC-0001 staff define, rename, retire and delete kinds of unit 07 Kind retirement blocks placement until reactivation api test
Proves BR-CAP-MBR-STR-001-07Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Deactivate sections, attempt section creation and relocation, then reactivate the kind through replacement. Expected Retirement preserves existing sections and blocks placement work until reactivation. Data The FAA example records or equivalent records prepared within the isolated workspace. Bound to Source services-membership:tests/acceptance/structure/MBR-ACC-0004.acceptance.ts #MBR-ACC-0004 retiring the Section kind freezes every section in place 08 Unit and program references prevent kind removal api negative test
Proves BR-CAP-MBR-STR-001-08Preconditions An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case. Steps Attempt removal of a unit-used kind and a program-selected kind. Expected Both conflict responses leave the referenced kinds available. Data The FAA example records or equivalent records prepared within the isolated workspace. Bound to Source services-membership:tests/e2e/structure-api.e2e.spec.ts #the structure API, end to end in process › refuses to delete a unit type in use, 409 unit_type_in_use Next Capability Test Specification → ATS-MBR-STR-002 · Restructure units while preserving dated placement: Acceptance Test Set