Skip to content

FAS-MBR-STR-05Terms and Standing: Feature Acceptance Suite

Markdown

FAS-MBR-STR-05

Terms and Standing: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Product areaMembershipModuleOrganizational Structure, Membership Configuration and TermsRevision1

Read atservices-membership 5994c270react-console baf6dae3

Scenarios

5 scenarios proving FEAT-MBR-STR-05 as a whole.

01 Compute a membership period and interpret its standing behaviour proposed
Exercises
CAP-MBR-STR-015 CAP-MBR-STR-016
Relies on
ATS-MBR-STR-015-03 ATS-MBR-STR-016-03 ATS-MBR-STR-016-05
Preconditions
A dated anniversary offering, classification grace and continuity allowances are supplied.
Steps
[object Object]
Expected
The dated outputs and standing decisions agree at each supplied date, with continuity decided from the effective periods.
Data
Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source
CAP-MBR-STR-015,CAP-MBR-STR-016
02 An unsuitable reason preserves the original period interaction proposed
Exercises
CAP-MBR-STR-015 CAP-MBR-STR-016 CAP-MBR-STR-017
Relies on
ATS-MBR-STR-017-02 ATS-MBR-STR-016-02
Preconditions
A committed term covers today and the catalogue contains a suspension-only reason.
Steps
[object Object]
Expected
The action fails; its unchanged period keeps the original standing and continuity inputs.
Data
Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source
CAP-MBR-STR-015,CAP-MBR-STR-016,CAP-MBR-STR-017
03 Expiry, explained closure and late rejoin retain original joining lifecycle test
Exercises
CAP-MBR-STR-015 CAP-MBR-STR-016 CAP-MBR-STR-017
Relies on
ATS-MBR-STR-015-04 ATS-MBR-STR-016-03 ATS-MBR-STR-016-05 ATS-MBR-STR-016-06
Preconditions
An ended term has 60 days of grace and a termination reason; the later rejoin is outside reinstatement.
Steps
[object Object]
Expected
The expired dates stay intact, the rejoin starts a fresh anniversary period and continuity has two episodes while original joining remains.
Data
Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Bound to
Source
services-membership:tests/e2e/s04-lapse-and-rejoin.e2e.spec.ts#scenario 4: lapse, drop and rejoin through a staff term
04 Date decisions respect their calling boundary permissionnegative proposed
Exercises
CAP-MBR-STR-015 CAP-MBR-STR-016 CAP-MBR-STR-017
Relies on
ATS-MBR-STR-019-02 ATS-MBR-STR-019-04 ATS-MBR-STR-017-02
Preconditions
Configuration management and application-access contexts are prepared with valid reason fixtures.
Steps
[object Object]
Expected
Setup changes need management and application admission fails before access to workspace operations.
Data
Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source
CAP-MBR-STR-015,CAP-MBR-STR-016,CAP-MBR-STR-017
05 Live zero grace and leap-day calculation stay compatible regressionnegative proposed
Exercises
CAP-MBR-STR-015 CAP-MBR-STR-016
Relies on
ATS-MBR-STR-015-08 ATS-MBR-STR-016-03
Preconditions
A calendar rule ends in February of a leap year and the type overrides grace with zero.
Steps
[object Object]
Expected
The calculated end uses leap day; the next day lapses under zero grace and uses program grace after the override is cleared.
Data
Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source
CAP-MBR-STR-015,CAP-MBR-STR-016

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.