On this page
In this guide
Run realistic test journeys across your website, communications, operations, and fulfillment flow before accepting live activity.
Prepare a safe test
- Confirm that every test uses the intended test accounts or an approved production test method.
- Use clearly identifiable test records and only the minimum information required.
- Do not use a real patient’s medical, identity, or payment information for general workflow testing.
- Name one person to run the test and one person to verify the resulting activity in ScalerMD.
- Record the expected result at each handoff before the test begins.
Run the core scenarios
- 01
Complete a successful journey
Begin on the website, complete the required intake and checkout steps, and verify that the order appears with the expected product, patient, and timeline information.
- 02
Leave intake incomplete
Stop before submission, then verify that the record is shown as incomplete and that the approved resume or reminder flow works as expected.
- 03
Exercise an action-required outcome
Use an approved scenario to confirm how missing information, a declined transaction, or another supported exception is presented to the operator.
- 04
Verify communications
Confirm the intended email or message is sent once, uses the approved brand and support information, and leads the recipient to the correct destination.
- 05
Verify completion and cancellation paths
Confirm the available terminal states and make sure a cancelled or failed journey does not appear as successfully completed.
Verify each connected system
- Website and checkout: the correct product, campaign context, and patient journey are created.
- Email and messaging: approved communications are delivered once and contain working links.
- Marketing: configured acquisition information appears only in the approved reporting fields.
- Clinical operations: the required information is available without changing or implying a clinical decision.
- Payments and fulfillment: the test follows the approved non-live method and reports the expected state.
Record results and approve launch
- Keep the ScalerMD record identifier, timestamps, environment, scenario, expected result, and actual result.
- Capture visible errors without including patient information, credentials, or payment data.
- Assign every failed check to an owner and rerun it after correction.
- Treat a scenario as passed only after the expected result is visible in the responsible system.
- Repeat affected scenarios after changes to integrations, mappings, website forms, communications, or workflow rules.
Need more help?
Review the safe support options before sharing account context. Keep patient information and credentials out of ordinary email.