BDT-4252 Stepper Test Report

The stepper and Review now say "your loved one" at deal stage and "the deceased" at ticket stage, but the ticket's acceptance test is only partly met: Welcome-page copy still says "deceased". 8 of 9 journeys passed, 1 partly run. · prepared 5 Nov 2026 by the tester, for the PM and the bare-core devs
Watch these first: you can see them happen.

↗ Jira BDT-4252 ↗ PR #4704

What was wrong. At deal stage the NoK paperwork stepper and Review headings showed internal page names such as "About The Deceased", so a living person was called "the deceased".

What the change does. A page whose title holds a {variable} now shows that title, resolved ("About your loved one"). Other pages keep their name. Tested on review app baredev-pr-4704 at PR head 6f89bf0c: NSW fresh, resume after a real save, Review, ACT/QLD/VIC/SA/WA/TAS, ticket stage, step click and hidden pages. Server first paint was checked as well as the page after JavaScript.

Acceptance test: Partly met
Scenario: Deal stage has no references to 'the deceased'. Given the app/NoK ppwk is at deal stage. When the user views their NoK ppwk/goes through the paperwork flow. Then they do not see the term 'The Deceased' or any similar term indicating their loved one is deceased in any part of the NoK ppwk/experience.
Met for the stepper and Review headings, which the change touches. Not met for the whole experience: the Welcome page still says "deceased" at deal stage in every state tested (F-1), and the estate admin form stepper says "About The Deceased" (F-2). Neither is changed by the PR. Dev was not checked, but this is form content the PR does not touch.
⚠ OUTSIDE THE TICKET'S SCOPE — review these as separate changes:
  • refreshStageWording.js re-runs the hidden {dashboard_stage} formulas after saved answers load, so a form started at deal stage says "the deceased" once the funeral is at ticket stage. It changes how saved answers load for every NoK form: review it as its own change. See cards TJ-7 and TJ-8.

Not changed by this work. Your call.

  • F-1: Welcome page copy says "the deceased" at deal stage (the next-of-kin hierarchy text in all tested states, and "the deceased's next of kin" in VIC). The ticket's words say no such term anywhere. Change the form copy, or is it out of scope? There is also a "your loved ones's" typo in NSW.
  • F-2: the estate admin (pre-consultation) form stepper says "About The Deceased" on a deal-stage funeral. Can a NoK reach it at deal stage, and should it change?

The ticket did not say. Please overrule anything you disagree with.

#The ticket saidWhat we didWhy
1Associate the ticket with the TJ-1 dealUsed a dedicated deal "BDT-4252 R5 TJ-7 deal" for the deal to ticket moveThe association step failed on a tool bug (fixed by the tester) after the TJ-1 funeral was already used; a separate funeral kept the runs clean.
2D-2: review app instead of a shared test app: no PDFs or HubSpot sending were checked.

Outside this ticket. We changed nothing here.

New tickets suggested (the PO decides):

  • F-1: Welcome page still says "deceased" at deal stage
  • F-2: Estate admin stepper says "About The Deceased"
  • The script's own "pass=false" on TJ-1, TJ-2 and TJ-6 came from the Welcome legal text and a heading selector that found nothing. Each was judged from the screenshots and saved data instead.

Test apps and the HubSpot sandbox only.

  • HubSpot sandbox (portal 51119063, Heroku Dev), names "BDT-4252 R5 …": deals TJ-1 NSW, TJ-5 ACT/QLD/VIC/SA/WA/TAS, TJ-7 deal; tickets TJ-4 ticket and TJ-7 move (associated with the TJ-7 deal). All test funerals in dev. Nothing deleted. No customer data.

So nobody thinks it was checked.

  • Review headings at ticket stage: not run (needs saved answers at ticket stage).
  • Public quote-page stepper (/at_need/quote, /prepaid/quote): needs a submitted public quote that creates a deal. Not run.
  • Admin standalone review page: opens only for a completed form. Not run.
  • PDFs (admin Full Export still uses page names), brands other than bare, and the PR's Cypress and Playwright specs: not run.
  • trigger_review_for_signing_in_app keeping a saved value: only checked while it was empty.
How to use this page: each card is one test journey. Open it and watch the recording. Repeat the steps yourself if you want. Then tick validated and write notes in the box. Ticks and notes are saved in your browser only. Filter with the buttons at the top.
Validated by us TJ-1 Deal stage, NSW, fresh form Deal stage

A deal-stage funeral opens its NoK paperwork for the first time.

Steps to repeat

  1. Sandbox deal "BDT-4252 R5 TJ-1 NSW deal" makes a deal-stage funeral.
  2. Dev admin → Review App → baredev-pr-4704 → open the NoK form.

Prediction (written before the run)

Server paint: steps 4/5 blank. Then "About your loved one" and "About your loved one's family and relationships". No "deceased" in the stepper.

Result

As predicted. The only "deceased" on screen is Welcome-page text (F-1).

🎬 Screen recording of the run
📸 01-TJ-1-stepper.png

Your validation notes

Validated by us TJ-2 Deal stage, resume after a real save Deal stage

Save, reload, look at the server's first paint.

Steps to repeat

  1. Tick the Terms switch, Save & Next (POST returned 204).
  2. Reload.

Prediction (written before the run)

Saved loved_one_reference = "your loved one"; server paint already says "About your loved one".

Result

As predicted: 204; database holds "your loved one" with stage deal; the server HTML after reload had the right labels.

🎬 Screen recording of the run
📸 02-TJ-2-stepper-after-reload.png

Your validation notes

Validated by us TJ-3 Deal stage, Review page Deal stage

Review headings at deal stage.

Steps to repeat

  1. Walk to the Review page.

Prediction (written before the run)

Headings "About your loved one…"; "About the Death" excluded; no "deceased" in headings.

Result

As predicted.

🎬 Screen recording of the run
📸 03-TJ-3-review.png

Your validation notes

Needs your call TJ-4 Ticket stage stepper Ticket stage

A ticket-stage funeral should still say "the deceased".

Steps to repeat

  1. Sandbox ticket "BDT-4252 R5 TJ-4 ticket" (new funeral).
  2. Open the NoK form.

Prediction (written before the run)

"About the deceased" / "About the deceased's family and relationships"; Review headings the same.

Result

Stepper as predicted (and it shows the "deceased" search can find text). The Review part was not run, so the journey is only partly run.

🎬 Screen recording of the run
📸 NSW-stepper.png

Your validation notes

Validated by us TJ-5 Every state at deal stage Deal stage

ACT, QLD, VIC, SA, WA, TAS.

Steps to repeat

  1. One sandbox deal per state.
  2. Open each form and read the stepper.

Prediction (written before the run)

Steps 4/5 say "your loved one"; ACT has no double space; WA step 5 uses the page title.

Result

As predicted in all six. Welcome pages still say "deceased" (F-1).

🎬 Screen recording of the run
📸 ACT-stepper.png
📸 WA-stepper.png
📸 VIC-stepper.png

Your validation notes

Validated by us TJ-6 Stepper behaviour unchanged Deal stage

Click a renamed step, check hidden pages and numbering.

Steps to repeat

  1. Click step 4 from the Review page.

Prediction (written before the run)

Step 4 opens and is active; hidden pages stay hidden; numbering 1..N.

Result

As predicted. The script said fail only because its heading selector found nothing; the screenshot shows the heading.

🎬 Screen recording of the run
📸 01-TJ-6-after-click.png

Your validation notes

Validated by us TJ-7 The same funeral moves from deal stage to ticket stage OUTSIDE SCOPE Ticket stage

Paperwork saved at deal stage, then the case becomes a ticket.

Steps to repeat

  1. Deal "BDT-4252 R5 TJ-7 deal" saved with "your loved one".
  2. Ticket "BDT-4252 R5 TJ-7 move" associated with it (same funeral, read back in the database).
  3. Open the form; Save & Next (204); reload.

Prediction (written before the run)

Server first paint may still say "your loved one"; browser switches to "the deceased"; after save and reload the server says "the deceased".

Result

As predicted: first paint "your loved one", browser at once "About the deceased", 204, after reload the server says "About the deceased"; database loved_one_reference = "the deceased", stage ticket.

🎬 Screen recording of the run
📸 01-TJ-8-first-open.png
📸 02-TJ-8-after-reload.png

Your validation notes

Validated by us TJ-8 Reload keeps deal-stage wording OUTSIDE SCOPE Deal stage

A deal-stage funeral with saved answers is reloaded.

Steps to repeat

  1. Open the TJ-1 funeral again (no save); compare the database before and after.

Prediction (written before the run)

Labels stay "your loved one"; saved values unchanged.

Result

As predicted; database identical before and after. The signing trigger was empty, so keeping a saved value is proven only for empty.

🎬 Screen recording of the run
📸 02-checked.png

Your validation notes

Validated by us TJ-9 Estate admin form (another user of the stepper) Other pages

The estate admin form uses the same stepper component.

Steps to repeat

  1. Open the pre-consultation form of the TJ-1 funeral.

Prediction (written before the run)

Labels equal page names as before; no step disappears.

Result

As predicted: 8 steps, labels equal names, no JavaScript errors. See F-2 for its "About The Deceased" step.

🎬 Screen recording of the run
📸 02-TJ-7a-estate-admin.png

Your validation notes

Needs your call Suggest a new ticket F-1 Welcome page still says "deceased" at deal stage Found outside the ticket's scope
📌 Not changed by the PR (the PR says so). Dev was not checked; this is form content, not stepper code.

The Welcome page of the NoK form says "the deceased" at deal stage.

Steps to repeat

  1. Open any deal-stage NoK form (NSW, ACT, QLD, VIC, SA, TAS) and read the Welcome page.

Prediction (written before the run)

No "deceased" wording at deal stage, per the ticket's acceptance test.

Result

The next-of-kin hierarchy text says "deceased person" in the states tested, and VIC says "the deceased's next of kin". NSW has a "your loved ones's" typo. A new ticket should change the form copy (a PM call).

📸 ACT-stepper.png

Your validation notes

Needs your call Suggest a new ticket F-2 Estate admin stepper says "About The Deceased" Found outside the ticket's scope
📌 Unchanged by the PR. Unknown whether a NoK reaches this form at deal stage.

The estate admin form's step 4 is named "About The Deceased".

Steps to repeat

  1. Open the pre-consultation form of a deal-stage funeral.

Prediction (written before the run)

Not decided: the PM should say whether this form is in the ticket's "NoK experience".

Result

Step 4 reads "About The Deceased".

📸 02-TJ-7a-estate-admin.png

Your validation notes