Rhythm 2.0 Specifications

Appearance

ATS-ACC-CLS-014Retain the evidence and history of each close: Capability Test Specification

Markdown

ATS-ACC-CLS-014

Retain the evidence and history of each close: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-ACC-CLS-014

Design

Executed by
TST-ACC-CLS-017, TST-ACC-CLS-018, TST-ACC-CLS-021, TST-ACC-CLS-031, TST-ACC-CLS-032

KindAcceptance test setProduct areaAccountingModuleMonth-End ClosingRevision2

Read atservices-accounting f47cb263react-console baf6dae3

Retain the evidence and history of each close: Capability Test Specification ​

Coverage ​

Coverage records the cases specified here. Proposed cases and remaining variants need executable proof before qualification.

RuleScenarios or Finding
BR-CAP-ACC-CLS-014-01ATS-ACC-CLS-014-01, ATS-ACC-CLS-014-06
BR-CAP-ACC-CLS-014-02ATS-ACC-CLS-014-01
BR-CAP-ACC-CLS-014-03ATS-ACC-CLS-014-02, ATS-ACC-CLS-014-06
BR-CAP-ACC-CLS-014-04ATS-ACC-CLS-014-03
BR-CAP-ACC-CLS-014-05ATS-ACC-CLS-014-04
BR-CAP-ACC-CLS-014-06ATS-ACC-CLS-014-04, ATS-ACC-CLS-014-06
BR-CAP-ACC-CLS-014-07ATS-ACC-CLS-014-05, ATS-ACC-CLS-014-06

| BR-CAP-ACC-CLS-014-02 | ATS-ACC-CLS-014-08 |

Carry captured evidence through correction and customer data operations. Read the original record after reopening, export the first workspace and then erase its close history in dependency order. The record and export keep the captured payment evidence; erasure removes only the selected workspace and leaves the other workspace’s evidence available. The interaction scenario names related capabilities and the workflows it exercises in its structured evidence.

Coverage

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

Test Scenarios

8 scenarios proving CAP-ACC-CLS-014; 5 bound to an existing test.

01 Refuse duplicate or invalid snapshotsinvariantapinegativetest
Proves
BR-CAP-ACC-CLS-014-01 BR-CAP-ACC-CLS-014-02 INV-DOM-ACC-CLS-004-01 INV-DOM-ACC-CLS-004-02 INV-DOM-ACC-CLS-004-03 INV-DOM-ACC-CLS-004-04
Preconditions
A close already has its captured snapshot.
Steps
Attempt duplication, update, mismatched period and invalid document writes.
Expected
Database checks reject each attempt.
Data
Snapshot key, reference and document variants.
Bound to
services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#refuses the application role any update of a snapshot, which is written once
services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#refuses a snapshot that names a period other than its run’s, by the run’s foreign key
Source
services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#accounting.period_close_snapshots
02 Retain the close and correction storyinteractionapitest
Proves
BR-CAP-ACC-CLS-014-03
Preconditions
A successful close has a later reopen.
Steps
Read the original close record.
Expected
Captured evaluation remains with audit entries and linked correction history.
Data
A completed close followed by reopening.
Bound to
Source
services-accounting:modules/fiscal-close/tests/e2e/fiscal-close-runs.e2e.spec.js#answers the completed close’s record
03 Limit records to completed closesvalidationapinegativeproposed
Proves
BR-CAP-ACC-CLS-014-04
Preconditions
A failed close and a reopen exist.
Steps
Request their close records.
Expected
Both return not found.
Data
Run kinds without a completed close snapshot.
Source
services-accounting:modules/fiscal-close/services/runs/close-run-view.ts:closeRecordOf
04 Protect fixed run facts and referenced periodsinvariantapinegativetest
Proves
BR-CAP-ACC-CLS-014-05 BR-CAP-ACC-CLS-014-06 INV-DOM-ACC-CLS-001-10 INV-DOM-ACC-CLS-004-06
Preconditions
Runs and snapshots exist under their database constraints.
Steps
Change fixed run fields, omit required metadata and delete referenced records.
Expected
The invalid writes and dependent deletions are refused.
Data
Run metadata and reference violations.
Bound to
Source
services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#accounting.period_close_runs
05 Isolate retained evidence by workspaceboundaryapinegativetest
Proves
BR-CAP-ACC-CLS-014-07 INV-DOM-ACC-CLS-003-09
Preconditions
Two workspaces own separate runs and snapshots.
Steps
Read and attempt writes across their boundaries.
Expected
Foreign information is absent and foreign writes are refused.
Data
Two isolated histories.
Bound to
services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#refuses a snapshot written for another tenant, by the policy’s check
Source
services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#row-level security
06 Carry captured evidence through correction and customer data operationsinteractionapiproposed
Proves
BR-CAP-ACC-CLS-014-01 BR-CAP-ACC-CLS-014-03 BR-CAP-ACC-CLS-014-06 BR-CAP-ACC-CLS-014-07
Preconditions
A successful close contains reconciliation exceptions and a later reopen; a second workspace has its own history.
Steps
Read the original record after reopening, export the first workspace and then erase its close history in dependency order.
Expected
The record and export keep the captured payment evidence; erasure removes only the selected workspace and leaves the other workspace’s evidence available.
Data
A successful close contains reconciliation exceptions and a later reopen; a second workspace has its own history.
Source
rhythm-v2-docs:specs/accounting/close/design/workflows/WF-ACC-CLS-007-export-the-close-history-with-the-workspace-s-data.md#What It Does,services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#refuses the application role any update of a snapshot, which is written once,services-accounting:modules/fiscal-close/tests/e2e/fiscal-close-runs.e2e.spec.js#answers the completed close’s record,services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#refuses deleting a period a run names,services-accounting:modules/fiscal-close/tests/integration/db/fiscal-close.table.integration.spec.js#hides the run and the snapshot from another tenant
07 Inspect a record beyond the correction-history limitboundaryapiproposed
Proves
BR-CAP-ACC-CLS-014-08
Preconditions
A close is linked to one hundred and one distinguishable reopen requests.
Steps
Read the original record and compare linked runs with the ordered requests.
Expected
The oldest one hundred links are returned without continuation; the newest link is absent from that response.
Data
A close is linked to one hundred and one distinguishable reopen requests.
Source
services-accounting:modules/fiscal-close/services/persistence/period-close-runs.ts:listReopenRunsOfCloseRun
08 Reject an oversized captured document through persistenceboundaryapinegativetest
Proves
BR-CAP-ACC-CLS-014-02 INV-DOM-ACC-CLS-004-04
Preconditions
A close run exists and a totals document reaches the storage-size threshold.
Steps
Attempt to save its snapshot through application persistence.
Expected
The oversized totals document is refused and no invalid snapshot is saved.
Data
A close run exists and a totals document reaches the storage-size threshold.
Bound to
Source
services-accounting:modules/fiscal-close/tests/integration/services/persistence/period-close-snapshots.integration.spec.js#refuses a totals document of 512 kB or more

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.

Rhythm Software