Related-capability and workflow references identify the seams each scenario exercises. The lifecycle coverage record retains transitions that still need individual proof.
The pinned service and browser assertions support the registered bindings. Original test references remain beside each scenario so partial evidence and unresolved conformance remain reviewable.
Coverage
Rulecovered
Transitioncovered
Validationcovered
Permissioncovered
Edgegap: FND-ACC-BKS-063
Failuregap: FND-ACC-BKS-063
Boundarycovered
Concurrencycovered
Invariantcovered
Interactioncovered
Test Scenarios
15 scenarios proving CAP-ACC-BKS-002; 8 bound to an existing test.
01Require currencies before enablementtransitionapinegativetest
An application-authorized reader and administrator share the run-owned setup. A third principal lacks the relevant resource grant.
Steps
Read the relevant configuration as the reader, attempt each supported mutation, then repeat with the matching administrator grants. Repeat the reads without their resource grants.
Expected
The permission outcomes match the cited authorization rule, and refused mutations leave every configured value unchanged.
Data
Run-owned records for the stated setup; retain the initial values for comparison.
Run-owned records satisfy the preconditions of the referenced capability proofs.
Steps
Create a dated foreign quote, try removing its currency, delete the quote and repeat removal.
Expected
The quote blocks removal; after it is removed, unused currency removal succeeds.
Data
Run-owned records for the stated setup; retain the initial values for comparison.
Source
services-accounting:modules/books/tests/e2e/business-units.e2e.spec.js#answers 409 naming the currency, the unit and the kinds of account that use it,services-accounting:modules/books/tests/integration/services/persistence/exchange-rates.integration.spec.js#refuses changing the unit, the currency or the day: a rate’s identity is write-once
13Foreign accounts protect their enabled currencyinteractionbrowsertest
services-accounting:modules/books/tests/e2e/business-units.e2e.spec.js#answers 409 naming the currency, the unit and the kinds of account that use it,services-accounting:modules/books/tests/e2e/gl-accounts.e2e.spec.js#answers 400 to a currency the unit is not enabled for, in Rhythm 1.0’s words,services-accounting:modules/books/tests/e2e/gl-accounts.e2e.spec.js#stores the code trimmed and upper-cased, under the id from the lower-cased code
14Receiving destinations use the enabled currency setinteractionapiproposed
Run-owned records satisfy the preconditions of the referenced capability proofs.
Steps
Create local bank and merchant destinations in an enabled foreign currency, then try an unsupported one.
Expected
The enabled destinations save and the unsupported ones leave no receiving records.
Data
Run-owned records for the stated setup; retain the initial values for comparison.
Source
services-accounting:modules/books/tests/e2e/gl-accounts.e2e.spec.js#answers 400 to a currency the unit is not enabled for, in Rhythm 1.0’s words,services-accounting:modules/books/tests/e2e/bank-accounts.e2e.spec.js#answers 400 to another unit’s GL account, naming both units