Maintain the region catalogue: Acceptance Test Set

Coverage

Rule	Proved by
`BR-CAP-CRM-REG-001-01`	`ATS-CRM-REG-001-01`
`BR-CAP-CRM-REG-001-02`	`ATS-CRM-REG-001-02`
`BR-CAP-CRM-REG-001-03`	`ATS-CRM-REG-001-03`
`BR-CAP-CRM-REG-001-05`	`ATS-CRM-REG-001-04`
`BR-CAP-CRM-REG-001-06`	`ATS-CRM-REG-001-05`; see `FND-CRM-REG-002`
`BR-CAP-CRM-REG-001-07`	`ATS-CRM-REG-001-06`
`BR-CAP-CRM-REG-001-08`	`ATS-CRM-REG-001-07`
`BR-CAP-CRM-REG-001-10`	`ATS-CRM-REG-001-08`
`BR-CAP-CRM-REG-001-12`	`ATS-CRM-REG-001-09`; see `FND-CRM-REG-003`, `FND-CRM-REG-012`

Show evidence (sources, provenance, origins, pinned commits)

9 scenarios proving CAP-CRM-REG-001; 7 bound to an existing test.

01 Identifier validation preserves the legacy grammarapinegativetest

Proves: BR-CAP-CRM-REG-001-01
Preconditions: Regional creation is authorized.
Steps: Submit an identifier with a space and another combining permitted punctuation.
Expected: The invalid identifier receives a field-specific refusal; the valid identifier is accepted.
Data: An invalid spaced identifier and valid identifiers covering the accepted grammar.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 400 for an id with a space, naming the characters an id may hold
services-crm:modules/regions/tests/integration/db/regions.table.integration.spec.js#refuses an id outside the legacy grammar (a space)
services-crm:modules/regions/tests/integration/db/regions.table.integration.spec.js#accepts the characters of the legacy grammar (word characters, | and -)
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 400 for an id with a space, naming the characters an id may hold

02 Blank names prevent creationapinegativetest

Proves: BR-CAP-CRM-REG-001-02
Preconditions: The caller can create regions.
Steps: Submit creation without a name and with a name containing only spaces.
Expected: Both requests fail name validation and persist nothing.
Data: The authorized workspace requires no additional records.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 400 for a body with no name
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 400 naming the field for a name of nothing but spaces
services-crm:modules/regions/tests/integration/db/regions.table.integration.spec.js#refuses a blank name
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 400 for a body with no name

03 Generated and duplicate identifiers have distinct outcomesapinegativetest

Proves: BR-CAP-CRM-REG-001-03 BR-CAP-CRM-REG-001-04
Preconditions: A named region already exists.
Steps: Create without an identifier, then attempt another creation using the existing identifier.
Expected: The first receives a generated identifier and defaults active; the duplicate is rejected without modifying the original.
Data: A previously saved regional definition.
Bound to: services-crm:modules/regions/tests/integration/services/persistence/regions.integration.spec.js#generates an id when the client names none
services-crm:modules/regions/tests/integration/services/persistence/regions.integration.spec.js#refuses an id the tenant already uses
services-crm:modules/regions/tests/integration/services/persistence/regions.integration.spec.js#creates a region active by default
Source: services-crm:modules/regions/tests/integration/services/persistence/regions.integration.spec.js#generates an id when the client names none

04 Replacement requires a current versionapinegativeproposed

Proves: BR-CAP-CRM-REG-001-05
Preconditions: The saved region has version two.
Steps: Replace using version one, omit the version, then use version two.
Expected: The requests respectively conflict, fail validation and save at version three.
Data: A regional definition with an intervening edit.
Source: FND-CRM-REG-022

05 Replacement removes omitted fieldsapitest

Proves: BR-CAP-CRM-REG-001-06
Preconditions: The region has a description and external identifier.
Steps: Replace the region with its required name and current version while omitting those fields.
Expected: The omitted values clear and the version increases.
Data: A region carrying explanatory text.
Bound to: services-crm:modules/regions/tests/integration/services/persistence/regions.queries.integration.spec.js#the record a replace left › answers the whole record as the replace left it: the fields it did not state cleared, the version bumped
Source: services-crm:modules/regions/tests/integration/services/persistence/regions.queries.integration.spec.js#the record a replace left › answers the whole record as the replace left it: the fields it did not state cleared, the version bumped

06 Pagination preserves identifier orderapitest

Proves: BR-CAP-CRM-REG-001-07
Preconditions: Region identifiers include different letter cases.
Steps: Read small pages and continue from each returned position.
Expected: All records appear once in byte order, and the final page has no continuation.
Data: Five catalogue entries whose identifiers mix letter case.
Bound to: services-crm:modules/regions/tests/integration/services/persistence/regions.integration.spec.js#lists the tenant's regions in id order by bytes, a page at a time
services-crm:modules/regions/tests/integration/services/persistence/regions.queries.integration.spec.js#listRegions › answers the next page beginning where the first one ended
Source: services-crm:modules/regions/tests/integration/services/persistence/regions.integration.spec.js#lists the tenant's regions in id order by bytes, a page at a time

07 Reads are workspace-specificapinegativetest

Proves: BR-CAP-CRM-REG-001-08
Preconditions: A caller can access two workspaces.
Steps: Read and list one workspace’s region through the other workspace.
Expected: The single read returns not found and the list excludes the foreign region.
Data: Two distinct customer workspaces.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the regions › answers 404 for this tenant's region read in another tenant, to a context that covers both
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the regions › answers none of this tenant's regions to another tenant's list
services-crm:modules/regions/tests/integration/services/persistence/regions.integration.spec.js#never reads another tenant's region
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the regions › answers 404 for this tenant's region read in another tenant, to a context that covers both

08 An ambiguous create response does not duplicate the regionunittest

Proves: BR-CAP-CRM-REG-001-10
Preconditions: The drawer already chose the creation identifier.
Steps: Lose the first response and retry creation.
Expected: Lookup recovers the original region and no duplicate is created.
Data: A request double that loses the initial response.
Bound to: react-console:lib/configuration/regions.test.ts#the regions api writes (D-05, D-35, D-43) › creates a region under the id the drawer chose and finds it when the answer was lost
Source: react-console:lib/configuration/regions.test.ts#the regions api writes (D-05, D-35, D-43) › creates a region under the id the drawer chose and finds it when the answer was lost

09 Unchanged replacement still advances the versionapiproposed

Proves: BR-CAP-CRM-REG-001-12
Preconditions: The region stands at version two.
Steps: Replace it with the same fields and version.
Expected: The fields remain but the saved version becomes three.
Data: A single regional definition.
Source: services-crm:modules/regions/services/persistence/regions.ts:updateRegionRow