Rhythm 2.0 Specifications

Appearance

FAS-MBR-MEM-05Renewal Operations and Expiry Attention: Feature Acceptance Suite

Markdown

FAS-MBR-MEM-05

Renewal Operations and Expiry Attention: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-MBR-MEM-05
Capabilities
CAP-MBR-MEM-013, CAP-MBR-MEM-014
Executed by
TST-MBR-MEM-004, TST-MBR-MEM-238

Product areaMembershipModuleMemberships, Applications and Membership BillingRevision1

Read atservices-membership 5994c270react-console baf6dae3

Renewal Operations and Expiry Attention: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

This suite tests the seasonal renewal plan and the work that follows review. Composite cases connect settled billing actions to the expiry attention staff use during that season.

Interactions Between Capabilities ​

The composite cases test the effect of a change in one capability on the records and answers of another. Detailed reliance links identify the supporting capability scenarios; an executable binding requires assertions for the complete feature case. Cases without such a binding remain proposed.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish cumulative feature coverage from the pinned specification and executable evidence.

Scenarios

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

01 Review a renewal plan before executing its work behaviour proposed
Exercises
CAP-MBR-MEM-013
Relies on
ATS-MBR-MEM-013-02 ATS-MBR-MEM-013-06 ATS-MBR-MEM-013-08
Preconditions
A reusable template selects renewing and lapsed members.
Steps
[object Object]
Expected
The reviewed run keeps its copied settings and settles the planned orders, notices and drops with observable action outcomes.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Source
services-membership:tests/e2e/billing-api.e2e.spec.ts#creates a template,services-membership:modules/billing/tests/unit/run-plan.spec.ts#counts the candidates, their classes, the exclusions and the planned actions,services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#executes on the jobs engine: one order per renewing candidate (Jo’s with both dues chapters), a notice and reminder each, one drop per lapsed term
02 Make a billing drop remove its expiry attention interaction proposed
Exercises
CAP-MBR-MEM-013 CAP-MBR-MEM-014
Relies on
ATS-MBR-MEM-013-08 ATS-MBR-MEM-014-07
Preconditions
Publication is enabled and a lapsed candidate has an open expiry item.
Steps
[object Object]
Expected
The configured drop reason is recorded and the existing item resolves with the closing write.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Source
services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#executes on the jobs engine: one order per renewing candidate (Jo’s with both dues chapters), a notice and reminder each, one drop per lapsed term,services-membership:modules/memberships/tests/integration/services/expiring-memberships.integration.spec.ts#resolves the item renewed in the staff renewal’s transaction
03 Create one planned run for a repeated scheduled occurrence lifecycle test
Exercises
CAP-MBR-MEM-013
Relies on
ATS-MBR-MEM-013-10 ATS-MBR-MEM-013-11
Preconditions
An active recurring configuration has a due local occurrence date.
Steps
[object Object]
Expected
Both deliveries refer to one run with one plan for the intended business day.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Bound to
Source
services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts,services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#creates and plans one run per occurrence of a recurring run, a redelivered occurrence finding it,services-membership:modules/billing/tests/integration/recurring-billing-run-concurrency.integration.spec.ts#applies one of two changes made at the same version and refuses the other with version_mismatch
04 Allow billing inspection while refusing planning to a reader permissionnegative test
Exercises
CAP-MBR-MEM-013
Relies on
ATS-MBR-MEM-013-12
Preconditions
A manager creates a template and its run; a reader has only billing-read authority.
Steps
[object Object]
Expected
The run reads successfully and planning returns a forbidden response.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Bound to
Source
services-membership:tests/e2e/billing-api.e2e.spec.ts,services-membership:tests/e2e/billing-api.e2e.spec.ts#lets a reader read the run and refuses it the planning
05 Leave planned renewal work stale after a term correction regression proposed
Exercises
CAP-MBR-MEM-013 CAP-MBR-MEM-014
Relies on
ATS-MBR-MEM-013-07 ATS-MBR-MEM-014-07
Preconditions
A renewing member has a planned order action and an enabled expiry item.
Steps
[object Object]
Expected
The stale action places no order and cannot resolve expiry attention as if a renewal had committed.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Source
services-membership:modules/billing/tests/integration/billing-runs.integration.spec.ts#refuses as stale an action whose term changed after planning,services-membership:modules/memberships/tests/integration/services/expiring-memberships.integration.spec.ts#resolves the item renewed in the staff renewal’s transaction

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