Rhythm 2.0 Specifications

Appearance

FAS-MBR-MEM-03Membership Purchases and Payment Consequences: Feature Acceptance Suite

Markdown

FAS-MBR-MEM-03

Membership Purchases and Payment Consequences: Feature Acceptance Suite

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-MBR-MEM-03
Capabilities
CAP-MBR-MEM-009, CAP-MBR-MEM-010
Executed by
TST-MBR-MEM-240, TST-MBR-MEM-241

Product areaMembershipModuleMemberships, Applications and Membership BillingRevision1

Read atservices-membership 5994c270react-console baf6dae3

Membership Purchases and Payment Consequences: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

This suite tests the purchase lifecycle from preparation and reservation to fulfilment, release and cancellation. Composite cases expose the effect of an outstanding reservation or cancellation on a competing purchase.

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-03 as a whole.

01 Make purchased rights visible only after fulfilment behaviour test
Exercises
CAP-MBR-MEM-009
Relies on
ATS-MBR-MEM-009-01 ATS-MBR-MEM-009-10 ATS-MBR-MEM-009-12 ATS-MBR-MEM-010-07
Preconditions
A new person has a package with an optional dues-bearing chapter.
Steps
[object Object]
Expected
Preparation changes nothing; placement reserves coverage; fulfilment produces one numbered holding and replay returns the same records.
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/commerce-purchase.e2e.spec.ts,services-membership:modules/commerce-participant/tests/unit/purchase-plan.spec.ts#carries no amount anywhere,services-membership:modules/commerce-participant/tests/integration/participant.integration.spec.ts#claims under the capability role: a pending, unnumbered membership with its pending term and claim,services-membership:modules/commerce-participant/tests/integration/participant.integration.spec.ts#fulfils: committed with its authorization, numbered, its chapter written with the dues product, enrolled,services-membership:modules/commerce-participant/tests/integration/participant.integration.spec.ts#releases a voided order: the pending term and the membership the claim created are deleted
02 Release reserved dates before a replacement purchase interaction proposed
Exercises
CAP-MBR-MEM-009 CAP-MBR-MEM-010
Relies on
ATS-MBR-MEM-009-10 ATS-MBR-MEM-010-07
Preconditions
A first purchase or renewal owns pending coverage.
Steps
[object Object]
Expected
The released claim no longer blocks replacement; an existing renewed holding survives release while an empty first-purchase holding does not.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Source
services-membership:modules/commerce-participant/tests/integration/participant.integration.spec.ts#claims under the capability role: a pending, unnumbered membership with its pending term and claim,services-membership:modules/commerce-participant/tests/integration/participant.integration.spec.ts#releases a voided order: the pending term and the membership the claim created are deleted
03 Close purchased coverage while fencing competing renewal lifecycle test
Exercises
CAP-MBR-MEM-009 CAP-MBR-MEM-010
Relies on
ATS-MBR-MEM-009-05 ATS-MBR-MEM-010-05 ATS-MBR-MEM-010-06 ATS-MBR-MEM-010-09
Preconditions
A package purchase is fulfilled with a chapter affiliation.
Steps
[object Object]
Expected
The competing purchase is refused while fenced; cancellation closes the term and chapter and clears the fence; replay returns the same records.
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/commerce-cancellation.e2e.spec.ts,services-membership:modules/commerce-participant/tests/unit/eligibility.spec.ts#refuses a suspended membership,services-membership:tests/e2e/commerce-cancellation.e2e.spec.ts#fences the membership in TX-K, refusing a competing purchase meanwhile,services-membership:tests/e2e/commerce-cancellation.e2e.spec.ts#answers a redelivered cancel obligation with the same records,services-membership:tests/e2e/commerce-cancellation.e2e.spec.ts#terminates the term the day before the effective date, ends its chapter, clears the fence
04 Distinguish the member’s cancellation from staff authority permissionnegative proposed
Exercises
CAP-MBR-MEM-009 CAP-MBR-MEM-010
Relies on
ATS-MBR-MEM-009-12 ATS-MBR-MEM-010-04
Preconditions
A member has both a pending purchase and started purchased coverage.
Steps
[object Object]
Expected
The pending cancellation can proceed for the member; started coverage requires approval for the member while staff preparation can proceed.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Source
services-membership:modules/commerce-participant/tests/integration/participant.integration.spec.ts#fulfils: committed with its authorization, numbered, its chapter written with the dues product, enrolled,services-membership:tests/acceptance/commerce/MBR-ACC-0335.acceptance.ts#MBR-ACC-0335
05 Keep paid coverage unique under delivery replay regression proposed
Exercises
CAP-MBR-MEM-009 CAP-MBR-MEM-010
Relies on
ATS-MBR-MEM-009-12 ATS-MBR-MEM-010-06
Preconditions
A fulfilled purchase can subsequently be cancelled.
Steps
[object Object]
Expected
Each replay returns the original records without adding another period, closure or business event.
Data
An isolated workspace, dated member fixtures, chapter and package configuration, and recording partner ports where the case requires them.
Source
services-membership:modules/commerce-participant/tests/integration/participant.integration.spec.ts#fulfils: committed with its authorization, numbered, its chapter written with the dues product, enrolled,services-membership:tests/e2e/commerce-cancellation.e2e.spec.ts#answers a redelivered cancel obligation with the same records

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