Use case: Healthcare
End-to-end testing for healthcare portals
Healthcare products run scheduling, intake forms, portals and consent flows, where a broken form stops a patient from reaching care.
Flows to cover first in healthcare: scheduling, intake forms, portals, consent. Each flow becomes a spec: a YAML file with plain-English steps that runs locally or in CI.
- Point tests at a staging environment with test patients. The platform does not need production data to run a test.
- Consent steps get an assert, so a consent screen that stops appearing fails the test.
- Long intake forms change often. Locator and layout changes are healed and recorded for review.
1name: Patient books an appointment2url: https://portal.example.com3tags: [scheduling, smoke]4env:5 EMAIL: ${TEST_PATIENT_EMAIL}6 PASSWORD: ${TEST_PATIENT_PASSWORD}7steps:8 - Log in with EMAIL and PASSWORD9 - Click "Book an appointment"10 - Choose the first free slot next week11 - assert: The consent notice is shown before confirming12 - Click "Confirm"13 - assert: The appointment appears under "Upcoming"Capabilities used
Tests in plain English
A test is a list of steps in plain English in a YAML file; the platform resolves each step against the live page at run time.
Read moreHeals locator and layout changes
When a step no longer resolves because an element moved, was renamed or restyled, the platform re-resolves it, marks the test as healed and records the change for review.
Read moreRuns in CI
One CLI command runs a suite in CI and reports a pass, fail or healed status per test as a check on the pull request.
Read moreCommon integrations
Questions
Should the tests use real patient data?
No. Run the tests against a staging environment with test patients.
Does the platform check accessibility?
No. It does not replace accessibility review.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.