Skip to content

ATS-ACC-BKS-006Assign accounts to standard posting purposes: Capability Test Specification

Markdown

ATS-ACC-BKS-006

Assign accounts to standard posting purposes: Capability Test Specification

Markdown
  • DocumentProposed
  • Product intentProposed

KindAcceptance test setProduct areaAccountingModuleBooks, Business Units and Chart of AccountsRevision2

Read atservices-accounting f47cb263react-console baf6dae3

Coverage

  • Rule covered
  • Transition not-applicable
  • Validation covered
  • Permission covered
  • Edge gap: FND-ACC-BKS-067
  • Failure gap: FND-ACC-BKS-067
  • Boundary covered
  • Concurrency covered
  • Invariant gap: FND-ACC-BKS-067
  • Interaction covered

Test Scenarios

8 scenarios proving CAP-ACC-BKS-006; 6 bound to an existing test.

01 Expose every default purposeruleapitest
Proves
BR-CAP-ACC-BKS-006-01
Preconditions
The unit has no assignments.
Steps
Read its defaults and the purpose vocabulary.
Expected
All fifteen ordered purposes are returned with expected types and empty assignments.
Data
The setup needs no extra fixture records.
Bound to
Source
services-accounting:modules/books/tests/e2e/default-gl-accounts.e2e.spec.js#answers all fifteen purposes in display order, with the count
02 Replace only eligible assignmentsvalidationapinegativetest
Proves
BR-CAP-ACC-BKS-006-02 INV-DOM-ACC-BKS-002-03 INV-DOM-ACC-BKS-002-06
Preconditions
Two units and an inactive account exist.
Steps
Assign across units, assign an inactive account and replace a valid assignment twice.
Expected
Invalid choices fail; valid replacement leaves one current assignment.
Data
The setup needs no extra fixture records.
Bound to
Source
services-accounting:modules/books/tests/e2e/default-gl-accounts.e2e.spec.js#answers 400 to another unit’s GL account, naming both units
03 Use unit permissions for defaultspermissionapinegativetest
Proves
BR-CAP-ACC-BKS-006-03
Preconditions
The caller can read but cannot update business units.
Steps
Read, assign and clear defaults.
Expected
Reading succeeds and both mutations receive permission refusals.
Data
The setup needs no extra fixture records.
Bound to
Source
services-accounting:modules/books/tests/e2e/default-gl-accounts.e2e.spec.js#lets a principal holding only accounting.business-units.read list the defaults
04 Resolve the chart’s missing-default noticeinteractionbrowsertest
Proves
BR-CAP-ACC-BKS-006-07
Preconditions
The unit has accounts but no defaults.
Steps
Open its chart and complete the assignment drawer.
Expected
The gaps appear in the notice; saved assignments read back and remove it.
Data
The setup needs no extra fixture records.
Bound to
Source
react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0008.spec.ts#ACT-ACC-0008
05 Clear an already empty assignmentboundaryapinegativeproposed
Proves
BR-CAP-ACC-BKS-006-04
Preconditions
An isolated workspace has records needed for both eligible and ineligible examples.
Steps
Clear an assigned purpose twice, then read the purpose list.
Expected
Both clears succeed and the complete purpose list contains an empty selection for that purpose.
Data
Run-owned records for the stated setup; retain the initial values for comparison.
Source
services-accounting:modules/books/tests/integration/services/persistence/default-gl-accounts.integration.spec.js#answers the purpose with no account when clearing a purpose the unit has no default for
06 Keep one destination during competing assignmentsconcurrencyapiproposed
Proves
BR-CAP-ACC-BKS-006-02 INV-DOM-ACC-BKS-002-06
Preconditions
Two active eligible accounts belong to one unit and both administrators can assign its defaults.
Steps
Assign both accounts to the same purpose from independent connections, then read the assignment and its stored rows.
Expected
Every accepted request leaves one current eligible destination; no duplicate purpose assignment survives.
Data
Run-owned records for the stated setup; retain the initial values for comparison.
Source
services-accounting:modules/books/db/business-unit-default-gl-accounts.table.ts
07 Tax posting follows the available destination choiceinteractionbrowsertest
Proves
BR-CAP-ACC-BKS-006-06 BR-CAP-ACC-BKS-013-02
Preconditions
Run-owned records satisfy the preconditions of the referenced capability proofs.
Steps
Post equivalent taxed work with a rate-specific account, only a unit default, and neither choice.
Expected
The three outcomes follow the cited destination resolution rule.
Data
Run-owned records for the stated setup; retain the initial values for comparison.
Bound to
Source
services-accounting:docs/architecture/accounting-2.0/02-decisions.md#A-1,react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0022.spec.ts#ACT-ACC-0022
08 Supply the allowance destination before retrying a write-offinteractionbrowsertest
Proves
BR-CAP-ACC-BKS-006-06 BR-CAP-ACC-BKS-003-02
Preconditions
A unit uses allowance write-offs but has no allowance default; its run-owned write-off awaits posting.
Steps
Post the pending work, inspect the missing-destination failure, assign the allowance default and retry the posting.
Expected
The configured destination changes the later posting outcome while the earlier failure remains recorded.
Data
Run-owned postable unit, write-off and active local allowance account.
Bound to
Source
react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0003.spec.ts#ACT-ACC-0003

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.