Set a program’s affiliation requirements: Acceptance Test Set

Coverage

Rule	Proof Scenario or Open Finding
`BR-CAP-MBR-STR-010-01`	`ATS-MBR-STR-010-01`
`BR-CAP-MBR-STR-010-02`	`ATS-MBR-STR-010-02`
`BR-CAP-MBR-STR-010-03`	`ATS-MBR-STR-010-03`
`BR-CAP-MBR-STR-010-04`	`ATS-MBR-STR-010-04`

Test Scenarios

4 scenarios proving CAP-MBR-STR-010; 1 bound to an existing test.

01 Program requirements replace at the read versionapinegativeproposed

Proves: BR-CAP-MBR-STR-010-01
Preconditions: An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case.
Steps: Replace unit requirements with the current program version and repeat with the earlier version.
Expected: The list saves once, advances the program version and rejects the stale retry.
Data: The FAA example records or equivalent records prepared within the isolated workspace.
Source: services-membership:modules/configuration/services/configuration/configuration-records.ts:replaceProgramUnitTypesOf

02 Non-affiliation programs reject populated requirementsapinegativeproposed

Proves: BR-CAP-MBR-STR-010-02
Preconditions: An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case.
Steps: Submit a nonempty category list for a program without unit binding.
Expected: The request fails without changing the program list.
Data: The FAA example records or equivalent records prepared within the isolated workspace.
Source: services-membership:modules/configuration/services/configuration/configuration-records.ts:replaceProgramUnitTypesOf

03 All invalid unit rows are reportedapinegativeproposed

Proves: BR-CAP-MBR-STR-010-03
Preconditions: An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case.
Steps: Submit an affiliation-disabled category, a repeated category and contradictory counts together.
Expected: The refusal identifies all detected row problems.
Data: The FAA example records or equivalent records prepared within the isolated workspace.
Source: services-membership:modules/configuration/services/configuration/configuration-records.ts:unitTypeProblems

04 Current affiliations protect their categoryapinegativetest

Proves: BR-CAP-MBR-STR-010-04
Preconditions: An isolated Membership-licensed workspace contains the relevant records, with caller permissions selected for the case.
Steps: Remove a kind still used by an open qualifying affiliation.
Expected: The list replacement fails and retains the category.
Data: The FAA example records or equivalent records prepared within the isolated workspace.
Bound to: services-membership:modules/memberships/tests/integration/services/affiliations.integration.spec.ts#the term affiliations in the database › refuses to drop a unit type from the program while an affiliation uses it (unit_type_in_use)
Source: services-membership:modules/memberships/tests/integration/services/affiliations.integration.spec.ts#the term affiliations in the database › refuses to drop a unit type from the program while an affiliation uses it (unit_type_in_use)