Rhythm 2.0 Specifications

Appearance

FAS-ACC-BKS-03Calendar Coverage acceptance

Markdown

FAS-ACC-BKS-03

Calendar Coverage acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-ACC-BKS-03
Capabilities
CAP-ACC-BKS-009, CAP-ACC-BKS-010
Executed by
TST-ACC-BKS-018, TST-ACC-BKS-047, TST-ACC-BKS-187

Product areaAccountingModuleBooks, Business Units and Chart of AccountsRevision1

Read atservices-accounting f47cb263react-console baf6dae3

Calendar Coverage: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The feature gives accounting work usable calendar coverage and a way to resolve dates within it. Acceptance follows explicit extensions, maintained names and the period standing supplied by Close.

Interactions Between Capabilities ​

A missing period changes the outcome of scheduled work. Extending coverage changes a later lookup without rewriting the failure already recorded.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish the feature’s cumulative acceptance boundary and record unimplemented joined outcomes.

Scenarios

5 scenarios proving FEAT-ACC-BKS-03 as a whole.

01 Maintain coverage and resolve dates through it behaviour test
Exercises
CAP-ACC-BKS-009 CAP-ACC-BKS-010
Relies on
ATS-ACC-BKS-009-01 ATS-ACC-BKS-009-05 ATS-ACC-BKS-010-02
Preconditions
A July-start unit has its two initial years.
Steps
Generate the next year, rename it, inspect its periods and resolve dates in generated years and beyond coverage.
Expected
The explicit extension supports date lookup and renaming preserves period identities and dates.
Data
Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases.
Bound to
Source
react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0023.spec.ts#ACT-ACC-0023
02 Restore a scheduled roll by extending coverage interaction test
Exercises
CAP-ACC-BKS-009 CAP-ACC-BKS-010 CAP-ACC-BKS-018
Relies on
ATS-ACC-BKS-010-03 ATS-ACC-BKS-009-01 ATS-ACC-BKS-018-05
Preconditions
A run-owned recurring subject has an occurrence after generated coverage.
Steps
Run the uncovered occurrence, explicitly generate the needed year and run a subsequent eligible occurrence.
Expected
The failed history remains visible and the later roll records a covered year and period.
Data
Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases.
Bound to
Source
services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#fails the roll dated in no fiscal year of the unit, with the sentence naming the date and the unit
03 Reflect period standing without rewriting coverage lifecycle proposed
Exercises
CAP-ACC-BKS-009 CAP-ACC-BKS-010
Relies on
ATS-ACC-BKS-009-07 ATS-ACC-BKS-010-01
Preconditions
A year has twelve open periods and a following generated year.
Steps
Close all periods through their owning workflow, inspect year standing and current lookup, then reopen one period through that workflow and inspect again.
Expected
Year standing and period lookup agree after both lifecycle changes; generation records keep their dates.
Data
Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases.
Source
ATS-ACC-BKS-009-07,ATS-ACC-BKS-010-01
04 Keep calendar maintenance separate from lookup access permissionnegative test
Exercises
CAP-ACC-BKS-009 CAP-ACC-BKS-010
Relies on
ATS-ACC-BKS-016-01 ATS-ACC-BKS-010-02
Preconditions
A reader can inspect an isolated generated calendar.
Steps
Read years and both period lookups, attempt generation, rename and deletion, and compare the calendar.
Expected
Reader lookup remains available and each maintenance attempt is refused without changing coverage.
Data
Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases.
Bound to
Source
services-accounting:modules/books/tests/e2e/configuration-security.e2e.spec.js#is refused a generation 403 permission_missing
05 Preserve coverage after an excessive extension request regressionnegative proposed
Exercises
CAP-ACC-BKS-009 CAP-ACC-BKS-010
Relies on
ATS-ACC-BKS-009-03 ATS-ACC-BKS-010-02
Preconditions
The latest generated year is near the permitted start-date horizon.
Steps
Record a date lookup, request a multi-year extension with one out-of-range year, then reread coverage and the original lookup.
Expected
The refused extension adds no partial year and preserves the previously resolved period.
Data
Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases.
Source
ATS-ACC-BKS-009-03,ATS-ACC-BKS-010-02

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