Rhythm 2.0 Specifications

Appearance

ATS-ACC-BAT-008Bring waiting batches to the posting team’s attention: Capability Test Specification

Markdown

ATS-ACC-BAT-008

Bring waiting batches to the posting team’s attention: Capability Test Specification

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Proves capability
CAP-ACC-BAT-008

Design

Executed by
TST-ACC-BAT-082, TST-ACC-BAT-120

KindAcceptance test setProduct areaAccountingModuleBatch ManagementRevision2

Read atservices-accounting f47cb263react-console baf6dae3rhythm-v2-docs 37405d50

Bring waiting batches to the posting team’s attention: Capability Test Specification ​

Coverage ​

The scenarios define focused checks for this outcome. The coverage map distinguishes specified checks from unresolved proof; executable bindings identify inspected assertions and carry no execution result.

RuleProof Specification or Gap
BR-CAP-ACC-BAT-008-01ATS-ACC-BAT-008-01, ATS-ACC-BAT-008-06
BR-CAP-ACC-BAT-008-02ATS-ACC-BAT-008-02
BR-CAP-ACC-BAT-008-03ATS-ACC-BAT-008-02
BR-CAP-ACC-BAT-008-04ATS-ACC-BAT-008-03, ATS-ACC-BAT-008-07, ATS-ACC-BAT-008-08, ATS-ACC-BAT-008-09
BR-CAP-ACC-BAT-008-05ATS-ACC-BAT-008-04
BR-CAP-ACC-BAT-008-06ATS-ACC-BAT-008-05
BR-CAP-ACC-BAT-008-07FND-ACC-BAT-062

New intake does not start posting attention. Reopening retires one attention generation. Deletion resolves posting attention. Posting resolves waiting attention. These checks use the related capability’s outcome as part of the setup or verification. Unbound interactions remain proposed until a suite executes the complete chain.

Coverage

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

Test Scenarios

9 scenarios proving CAP-ACC-BAT-008; 5 bound to an existing test.

01 Waiting status is specific to transaction batchesruleunittest
Proves
BR-CAP-ACC-BAT-008-01
Preconditions
Transaction batches cover all statuses and a system batch is present.
Steps
Evaluate whether each awaits posting.
Expected
Only Closed, Verified, Posting and Error transaction batches qualify.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/unit/attention/batches-awaiting-posting.spec.js#holds for a transaction batch in exactly closed, verified, posting and error
02 Close creates the attention itemtransitionapitest
Proves
BR-CAP-ACC-BAT-008-02 BR-CAP-ACC-BAT-008-03
Preconditions
The batch starts Open.
Steps
Retrieve attention items, close the batch and retrieve them again.
Expected
Open has none; closing creates one open item with the expected mapping.
Data
Provide accounting's attention publisher in process.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#publishes one open item of the batch with every element mapped
03 Leaving the waiting set resolves attentioninteractionapitest
Proves
BR-CAP-ACC-BAT-008-04
Preconditions
Four Closed batches have attention items.
Steps
Post, reopen, archive and delete them respectively, then close the reopened record again.
Expected
Each original item resolves with its outcome; the repeated close starts a new generation.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#resolves a reopened batch reopened, and its next close opens the second generation
04 Allowances determine deadlinesboundaryunitnegativetest
Proves
BR-CAP-ACC-BAT-008-05
Preconditions
Posting allowances are five days, zero days, two and a half days, forty-five days and absent.
Steps
Calculate a deadline from each close time.
Expected
Five days preserves the close’s wall-clock time and zero uses the close itself; fractional, oversized and absent values use the two-day default.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/unit/attention/batches-awaiting-posting.spec.js#answers the default 2 for a missing, fractional, out-of-bounds or mistyped value
05 The sweep repairs attention stateinvariantapitest
Proves
BR-CAP-ACC-BAT-008-06
Preconditions
One waiting item is missing, another no longer qualifies and the allowance changed.
Steps
Run the workspace sweep.
Expected
It publishes the missing item, clears the obsolete one, refreshes deadlines and records the sweep time.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#publishes the batch whose item was lost
06 New intake does not start posting attentioninteractionapiproposed
Proves
BR-CAP-ACC-BAT-001-01 BR-CAP-ACC-BAT-008-01
Preconditions
Attention publication is enabled for the unit.
Steps
Create Morning without an automatic close and inspect its attention.
Expected
Morning is Open and has no waiting item.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/tests/e2e/batches.e2e.spec.js#refuses a create naming the status 400: a new batch is always open; services-accounting:modules/batches/tests/unit/attention/batches-awaiting-posting.spec.js#holds for a transaction batch in exactly closed, verified, posting and error
07 Reopening retires one attention generationinteractionapiproposed
Proves
BR-CAP-ACC-BAT-004-03 BR-CAP-ACC-BAT-008-04
Preconditions
Attention publication is enabled and Morning is Open.
Steps
Close Morning, inspect its attention, reopen it, then close it again.
Expected
The first item is resolved and the second close creates a new generation.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#clears the errors of an errored batch on reopen, so the open batch carries none (journey ACT-ACC-0521); services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#resolves a reopened batch reopened, and its next close opens the second generation
08 Deletion resolves posting attentioninteractionapiproposed
Proves
BR-CAP-ACC-BAT-006-07 BR-CAP-ACC-BAT-008-04
Preconditions
Attention publication is enabled for an unused Closed batch.
Steps
Delete the batch and inspect its formerly open attention item.
Expected
The batch is absent and its waiting item is resolved.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#deletes an empty batch with its automatic close’s schedule; services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#resolves a reopened batch reopened, and its next close opens the second generation
09 Posting resolves waiting attentioninteractionapiproposed
Proves
BR-CAP-ACC-BAT-008-04 BR-CAP-ACC-BAT-013-03
Preconditions
Attention publication is enabled and Morning is Closed with one eligible invoice.
Steps
Inspect the waiting item, post Morning and inspect the item again.
Expected
Morning is Posted and its waiting item is resolved.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/tests/integration/services/persistence/batch-attention-items.integration.spec.js#resolves a reopened batch reopened, and its next close opens the second generation; services-accounting:modules/batches/tests/e2e/batch-postings.e2e.spec.js#posts a batch as a durable job: the answer is the job, and the job posts the batch

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