MSD Price Change Test Plan

Steps

1. Run every PriceChange test class in UAT, with code coverage turned on.

Expected

• All tests pass.
• Each price change class has at least 75% coverage.

Steps

1. Create a Price Change with a description, Funder and go-live date.

Expected

• Status is Draft.
• Price rule defaults to Bills dated on or after go-live.
• The path shows step 1 and what to do next.

Steps

1. Click Add products.
2. Compare the list with the products that have live MSD subscriptions.

Expected

• One row per product, including inactive and grandfathered ones that still bill.
• Peripheral products are not added.
• Each row shows its frequency and price group.

Steps

1. Wait for the count to finish, or click Count subscriptions.

Expected

• Old price is the most common billed amount.
• The row shows live subscriptions and how many differ.

Check on the record

• A tie goes to the higher amount.
• A product with no live subscription keeps its pricebook price.

Steps

1. Open the price list in Draft.

Expected

• Rows show New price, Unchanged, No live subscriptions or No entry.
• The tiles add up to the number of rows.

Steps

1. Click Prices increased before the count finishes.

Expected

• Refused, with a message to count the live subscriptions first.
• Status stays Draft.

Steps

1. Click Prices increased.

Expected

• Refused, naming the product.
• No new price is copied.

Steps

1. Click Prices increased and confirm.
2. Try to edit a new price on a row.

Expected

• Incl and excl GST prices are copied from the pricebook, unchanged products too.
• Status is Pricebook Confirmed.
• The edit is refused: prices are locked.

Check on the record

• The confirmed-on date is set.
• No pricebook entry changed: last modified dates are as before.

Steps

1. Click Return to Draft and confirm.

Expected

• Status is Draft.
• New prices and the confirmed-on date are cleared.

Steps

1. Try to add a product row.

Expected

• Refused: products can only be added in Draft.

Steps

1. Open the price change as that user.
2. Try Prices increased, Apply now and Send to BC now.

Expected

• Each action is refused or disabled, with the reason shown.

Steps

1. Click Run preview.
2. Watch the progress bar until it finishes.

Expected

• Progress shows step 1 of 2 Building lines, then 2 of 2 Counting coverage.
• Status moves to Previewed by itself.
• The header shows lines, to apply and exceptions.

Steps

1. Open the Lines tab after the preview.
2. Compare the line count with live subscriptions on the 2 products.

Expected

• One line per live schedule of a changing product.
• No line for a product keeping its price.
• A check line counts subscriptions on products not changing.

Steps

1. Compare schedules, order lines, orders and Upcoming bills with the snapshot.

Expected

• 0 differences.

Steps

1. Click Run preview again.

Expected

• The line count is the same, with one line per schedule.
• Lines are updated, not added.

Steps

1. Return to Draft, restore one price, click Prices increased, then run the preview again.

Expected

• Lines that are only Already at the new price are gone.
• Real exceptions stay as Skipped.

Steps

1. Run the preview.
2. Open Price Change Lines by status.

Expected

• Not billing: no Upcoming bill.
• Not the latest live schedule on this order line (only the older one).
• Each is counted in the preview checks.

Steps

1. Run the preview.
2. Open the line and read Item Prices.

Expected

• One line for the schedule.
• New amount = new base price + the add-on's current total.
• Item Prices lists both order lines.

Steps

1. Run the preview and open the lines.
2. Click Apply now and read each schedule.

Expected

• Each line is flagged Not at list price and stays To re-price.
• After Apply: amount = new price x quantity + the add-on's current total.

Steps

1. Run the preview.
2. Release the hold and read the next bill.

Expected

• The line is Skipped: Not billing.
• Agree with Finance what the next bill should be. Today it stays at the old amount.

Steps

1. Run the preview and look in the checks.

Expected

• It is listed for Finance.

Steps

1. Change the go-live date.
2. Try Apply now.

Expected

• A message says prices, products or the go-live date changed.
• Apply is refused until the preview runs again.

Steps

1. Run the preview.

Expected

• Missing products tile shows 1.
• Reconcile can't pass until it is fixed.

Steps

1. Click Run preview again.

Expected

• The preview runs.
• Applied lines keep their status, amounts and sync state.
• The Error line is refreshed, and Apply now can retry it.

Steps

1. Add products, count, click Prices increased, run the preview.

Expected

• 0 lines, and status moves to Previewed.
• Missing products = 0.

Steps

1. Open the Apply card.

Expected

• No line is due; the next due date is shown.
• Apply now is disabled.

Steps

1. Note the old values.
2. Click Apply now and confirm.
3. Wait for it to finish.

Expected

• Lines are Applied; status moves to Applied.
• Records updated tiles count orders, order products and bills.

Check on the record

• Schedule: amount = New Amount.
• Order line: unit price = pricebook excl GST; line total = incl x quantity; GST = the difference.
• Upcoming bill: rate, total, GST and list value are new.
• Order: Action Required starts PRICE_CHANGE.
• Order totals unchanged.

Steps

1. Compare with the snapshot.

Expected

• No schedule or bill created.
• Start date, frequency, billing day and bank details unchanged.
• End Date still blank.

Steps

1. Run Apply.
2. Compare the bills with the snapshot.

Expected

• An Upcoming bill dated on or after go-live is at the new price.
• An Upcoming bill dated earlier stays at the old price.
• Submitted, Invoiced and On Hold bills are untouched.

Steps

1. Run Apply.

Expected

• The line is in Error, with both amounts in the message.
• Nothing on that order changed.
• Other lines apply.
• Status stays Previewed.

Steps

1. Run Apply.
2. Restore the price and click Apply now again.

Expected

• Lines of that product go to Error, naming the product and both prices.
• The second Apply retries and applies them.

Steps

1. Run Apply.

Expected

• The line is in Error, with the End Date in the message.
• Nothing on that order changed.

Steps

1. Run Apply.

Expected

• The line is not applied, and the reason is shown.
• Nothing on that order changed.

Steps

1. Run Apply.

Expected

• The line is in Error: the new prices don't add up to the preview's amount.
• Nothing on that order changed.

Steps

1. Click Apply now as that user.

Expected

• All due lines apply.

Steps

1. Read the sync messages and the lines.

Expected

• No Price Change Sync Message exists.
• Lines are Not Sent.
• The next hourly feeds may still carry these records; note what they send.

Steps

1. Read the order line and bill after Apply.

Expected

• Incl = pricebook incl x quantity, to the cent.
• GST = incl minus excl, to the cent.
• Schedule amount = the sum of the lines.

Steps

1. Click Send to BC now and confirm.
2. Watch the progress.

Expected

• 3 messages: Billing schedules, Order lines, Orders, in that order.
• Each message answers 200 or 201.
• Lines are Sent; status moves to Synced.

Check on the record

• Feeds Sent on each line = schedule;line;order.
• Latest messages link to their integration logs.

Steps

1. Send, then read the sync messages.

Expected

• 2 chunks, 6 messages.
• No message carries more than 200 lines.

Steps

1. Open the request in the integration log.

Expected

• Schedule: id, order, order number, status, amount.
• Order line: unit price, list price, line total, GST, quantity.
• Order: totals and Action Required.
• No wearer, date of birth, NHI or phone data.

Steps

1. Send.

Expected

• Lines go to Failed, with the feed and code in the error.
• A failed Sync Message is recorded.
• Status stays Applied.

Steps

1. Click Retry failed.

Expected

• Only the missing feed is sent.
• Lines become Sent once all three are in.
• Status moves to Synced.

Steps

1. Read the line and the message.

Expected

• The line is Failed: not confirmed as sent.
• It is never marked Sent without a 200 or 201.

Steps

1. Run the test.

Expected

• Lines are Failed, and the message says the switch is off.

Steps

1. Try Send to BC now.

Expected

• Disabled, saying a run is in progress.

Steps

1. Click Retry failed.

Expected

• All failed lines are sent again.

Steps

1. Check what the hourly feeds sent.
2. Check the same orders in BC test.

Expected

• BC holds the same prices.
• No duplicate price line or invoice.

Steps

1. Check 5 orders of each frequency in BC test.

Expected

• Schedule amount, unit price and line total match Salesforce.
• BC reads unit price and line total, not list price.

Steps

1. Check the same orders in BC test.

Expected

• No duplicate and no change.

Steps

1. Let the next billing run take them, or run it with an agreed go.

Expected

• Bills are Submitted at the new amount.
• The billing message carries the new amount.

Steps

1. Read the next Upcoming bill on each schedule.

Expected

• One next bill, at the new price, on the same schedule.
• Billing period follows on, with the same billing day.

Steps

1. Compare the invoices in BC test.

Expected

• Invoice amount = bill amount.
• No duplicate invoice.

Steps

1. Run AP-02 and BL-01 for each kind.

Expected

• Each has its first bill dated on or after go-live at the new price.
• An in-arrears period straddling go-live is billed in full at the new price.

Steps

1. Follow the go-live runbook timing in UAT.
2. Read the bill after the 03:00 run.

Expected

• Apply finished before the billing run.
• The bill is at the new price.

Steps

1. Create it and read its schedule.

Expected

• It bills at the new price.
• Finance Q4: website, TIS and quick create pick the price up.

Steps

1. Click Check now.
2. Click Apply now.

Expected

• A late line appears for it.
• Apply re-prices it, and Send to BC now sends it.

Steps

1. Cancel one service, swap one product, add a billing holiday.

Expected

• Each works as usual.
• One live schedule per subscription.

Steps

1. Open Reconcile and close.

Expected

• Products, coverage, applied, sent and nothing at the old price are ticked.
• First bills show when they are due.
• Close is disabled.

Steps

1. Click Check now.

Expected

• Left at old price = 1.
• Close stays disabled.

Steps

1. Click Check now on each date, or in a test with dates moved.

Expected

• Each frequency goes from due to OK.
• A wrong amount shows as at old price.

Steps

1. Click Check now.

Expected

• Agree with Finance if this should block Close.
• Today it counts as at old price, so Close stays disabled.

Steps

1. Click Close price change.

Expected

• Status is Closed.
• No further check or late-line sweep runs.

Steps

1. Try Close price change.

Expected

• Disabled or refused, saying every check must be ticked.

Steps

1. Run the preview and time it.

Expected

• One line per live schedule.
• No errors. Record the run time.

Steps

1. Click Apply now and time it.
2. Stop before 01:00, or roll back.

Expected

• All lines applied or explained.
• Record the run time; scale it to about 43,000.
• No record-lock errors.

Steps

1. Click Send to BC now and time it.

Expected

• All messages answer 200 or 201.
• Status moves to Synced.
• Record the run time.

Steps

1. Open the Lines tab; refresh.

Expected

• The preview and apply panels load with correct counts, with no limit errors.

Steps

1. Open Reconcile and close; click Check now.

Expected

• Checks show, and Left at old price = 0.
• Close works once all pass.

Steps

1. Restore the pricebook entries.
2. Update only rows that differ: schedules, order lines, Upcoming bills, orders.
3. Compare again.

Expected

• 0 differences, apart from bills already billed.
• New Upcoming bills are at the old price.

Steps

1. Back up, then delete lines, products and the header, in that order.

Expected

• The header can't be deleted while lines exist.
• No test price change is left.

Steps

1. Reverse or re-send them in BC test.
2. Credit any invoice raised at the test price.

Expected

• BC test matches Salesforce.