Use case: SaaS products
End-to-end testing for SaaS products
A SaaS product changes its settings pages, plans and roles often. The flows that break revenue or access are onboarding, billing, permissions and settings.
Flows to cover first in saas products: onboarding, billing, permissions, settings. Each flow becomes a spec: a YAML file with plain-English steps that runs locally or in CI.
- Permissions: one spec per role checks that a viewer cannot reach an admin page. A changed outcome fails the test instead of being healed.
- Billing: an API step checks the subscription state after the UI flow, in the same test.
- Settings pages are restyled often. Locator and layout changes are healed and recorded for review.
1name: Viewer cannot open billing settings2url: https://app.example.com3tags: [permissions, smoke]4env:5 EMAIL: ${VIEWER_EMAIL}6 PASSWORD: ${VIEWER_PASSWORD}7steps:8 - Log in with EMAIL and PASSWORD9 - Open the settings menu10 - assert: The menu has no "Billing" item11 - Go to /settings/billing12 - assert: The page says the user has no accessCapabilities 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 moreAPI stepsBeta
A step can call an HTTP endpoint and assert on the response, mixed with UI steps in the same test.
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
Which SaaS flows should have end-to-end tests first?
The ones that stop revenue or access when they break: sign-up and onboarding, billing, role permissions and core settings.
Can one test check both the UI and the API?
Yes. API steps are in beta and can be mixed with UI steps in the same test.
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.