Rhythm 2.0 Specifications

Appearance

ATS-ACC-BAT-005Arrange automatic close and posting: Capability Test Specification

Markdown

ATS-ACC-BAT-005

Arrange automatic close and posting: Capability Test Specification

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Proves capability
CAP-ACC-BAT-005

Design

Executed by
TST-ACC-BAT-085, TST-ACC-BAT-086

KindAcceptance test setProduct areaAccountingModuleBatch ManagementRevision2

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

Arrange automatic close and posting: 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-005-01ATS-ACC-BAT-005-01, ATS-ACC-BAT-005-06
BR-CAP-ACC-BAT-005-02ATS-ACC-BAT-005-02
BR-CAP-ACC-BAT-005-03ATS-ACC-BAT-005-03, ATS-ACC-BAT-005-10
BR-CAP-ACC-BAT-005-04ATS-ACC-BAT-005-03, ATS-ACC-BAT-005-09
BR-CAP-ACC-BAT-005-05ATS-ACC-BAT-005-04, ATS-ACC-BAT-005-07, ATS-ACC-BAT-005-08
BR-CAP-ACC-BAT-005-06ATS-ACC-BAT-005-05
BR-CAP-ACC-BAT-005-07ATS-ACC-BAT-005-11

Creation supplies a scheduled close. Removing the close time cancels delivery. Manual close cancels a scheduled close. Rolling does not duplicate a due close. Scheduled close submits accounting after retirement. 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 covered
  • Transition gap: FND-ACC-BAT-059
  • Validation covered
  • Permission gap: FND-ACC-BAT-059
  • Edge gap: FND-ACC-BAT-059
  • Failure covered
  • Boundary gap: FND-ACC-BAT-059
  • Concurrency gap: FND-ACC-BAT-059
  • Invariant covered
  • Interaction covered

Test Scenarios

11 scenarios proving CAP-ACC-BAT-005; 4 bound to an existing test.

01 Automatic close uses local-minute schedulingruleapitest
Proves
BR-CAP-ACC-BAT-005-01
Preconditions
The workspace uses New York time.
Steps
Create an Open batch with an offset-bearing close timestamp and inspect its schedule.
Expected
The batch retains one occurrence at the corresponding local minute in the workspace’s zone.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#keeps a one-occurrence schedule of the batch at that minute, in the tenant’s zone
02 Delivery checks whether closing still appliestransitionapinegativetest
Proves
BR-CAP-ACC-BAT-005-02
Preconditions
One due batch remains Open and another was closed manually.
Steps
Deliver both scheduled occurrences.
Expected
The Open batch closes and retains its ended schedule; the other occurrence records a skip reason.
Data
Provide the schedule consumer in process.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#skips a run whose batch is no longer open
03 Repeated delivery does not submit another postinginvariantapitest
Proves
BR-CAP-ACC-BAT-005-03 BR-CAP-ACC-BAT-005-04
Preconditions
An Open batch contains documents and has a close schedule.
Steps
Deliver the same occurrence twice.
Expected
Only one posting job is submitted for that unit’s batch.
Data
Provide the local job runner.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#submits one posting job of the closed batch, in its unit, for the tenant’s customer (D13)
04 Manual removal clears the close scheduleinteractionapitest
Proves
BR-CAP-ACC-BAT-005-05
Preconditions
Three Open batches have scheduled closes.
Steps
Close the first, archive the second and delete the third.
Expected
Each schedule and close time disappear, preventing a later run.
Data
Provide no fixtures beyond the stated setup.
Bound to
Source
services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#removes the schedule and the time when the batch is closed
05 Posting refusal preserves the closed batchfailureapinegativeproposed
Proves
BR-CAP-ACC-BAT-005-06
Preconditions
Automatic close has completed but the customer cannot be resolved.
Steps
Deliver the occurrence’s posting preparation.
Expected
The run retains the refusal, creates no job and leaves the batch Closed.
Data
Provide no fixtures beyond the stated setup.
Source
services-accounting:modules/batches/services/auto-post/automatic-posting.ts:prepareAutomaticPosting
06 Creation supplies a scheduled closeinteractionapiproposed
Proves
BR-CAP-ACC-BAT-001-01 BR-CAP-ACC-BAT-005-01
Preconditions
Today is open and tomorrow has a future close time.
Steps
Create Morning with tomorrow’s close time and retrieve its schedule.
Expected
Morning is Open and its one scheduled occurrence identifies the created batch.
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/integration/services/persistence/batches.integration.spec.js#keeps a one-occurrence schedule of the batch at that minute, in the tenant’s zone
07 Removing the close time cancels deliveryinteractionapiproposed
Proves
BR-CAP-ACC-BAT-003-01 BR-CAP-ACC-BAT-005-05
Preconditions
Morning is Open with a future close occurrence.
Steps
Clear its close time through details editing and inspect the saved batch and schedule.
Expected
Morning stays Open without its former close schedule.
Data
An isolated workspace with the stated business-unit calendar, documents and configuration.
Source
services-accounting:modules/batches/aws/api/batches.schemas.ts:batchPatchSchema; services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#removes the schedule and the time when the batch is closed
08 Manual close cancels a scheduled closeinteractionapiproposed
Proves
BR-CAP-ACC-BAT-004-02 BR-CAP-ACC-BAT-005-05
Preconditions
Morning is Open with a future close occurrence.
Steps
Close it manually and deliver the old occurrence after it is due.
Expected
Morning remains Closed and the old delivery cannot close it again.
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#refuses closing a batch that is not open; services-accounting:modules/batches/tests/integration/services/persistence/batches.integration.spec.js#removes the schedule and the time when the batch is closed
09 Rolling does not duplicate a due closeinteractionapinegativeproposed
Proves
BR-CAP-ACC-BAT-005-04 BR-CAP-ACC-BAT-010-06
Preconditions
A populated active batch has a due close and the stream is due to roll.
Steps
Deliver close and roll occurrences in both orders using separate fixtures.
Expected
Each fixture has one replacement intake batch; the predecessor has no duplicate current posting.
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#posts nothing more when the same occurrence runs again: the batch is no longer open; services-accounting:modules/batches/tests/integration/services/roll/batch-roller.integration.spec.js#opens nothing for the same occurrence delivered again, and answers the same batch
10 Scheduled close submits accounting after retirementinteractionapiproposed
Proves
BR-CAP-ACC-BAT-005-03 BR-CAP-ACC-BAT-013-03
Preconditions
Morning is Open with an invoice and a due close.
Steps
Deliver the occurrence and inspect its outcome and the submitted job.
Expected
Morning closes and the run identifies one posting request for the retired collection.
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#submits one posting job of the closed batch, in its unit, for the tenant’s customer (D13); 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
11 Past close times need an explicit refusalvalidationapinegativeproposed
Proves
BR-CAP-ACC-BAT-005-07
Preconditions
An Open batch is writable and yesterday is before the fixed current clock.
Steps
Submit yesterday as the automatic close time.
Expected
The proposed validation result refuses the request without saving the past occurrence.
Data
Owned records in an isolated workspace with the stated calendar and accounting setup.
Source
FND-ACC-BAT-005

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