From Mabl
Recreate Mabl recorded journeys as editable Smoketest tests.
Mabl journeys usually start as recordings. Smoketest tests are plain text, so migration starts by exporting or documenting the journey inventory, then rewriting each journey as user intent.
You do not need to preserve element models or healing history. Keep the business test and the visible result that proves it worked.
Translate the concepts
| Mabl | Smoketest |
|---|---|
| Browser test or journey | One test |
| Recorded interaction | Action step in words |
| Assertion | Verification step in words |
| Login test | Login sharedStep or environment-backed login steps |
| DataTable value | Representative test data or environment variable |
| Plan or stage | Project, tags, schedules, or deployment webhook |
| Failure replay | Run recording, screenshots, and run history |
What to migrate
Start with the journeys your team actually uses for release confidence: signup, login, checkout, billing, onboarding, admin workflows, and customer-facing dashboards.
Skip one-off exploratory recordings, API checks, synthetic data permutations, and tests that are no longer tied to shipped product behavior.
Build an inventory
If the tests are not in your repo, create a local migration file first:
# mabl-export.md
## Checkout with annual plan
Start URL: https://staging.example.com/pricing
Steps:
- Choose the annual plan.
- Continue to checkout.
- Verify the checkout page shows the annual plan.Quick migration prompt
Use $smoketest-explore to migrate the Mabl inventory in this repo to Smoketest.
1. Check Smoketest CLI install and auth first.
2. Read exported Mabl journey notes, screenshots, or local migration files such as mabl-export.md.
3. Convert each active browser journey into .smoketest/explore test drafts.
4. Rewrite recorded interactions as user-intent steps.
5. Use Smoketest environments for credentials and representative test data.
6. Skip inactive recordings, API-only checks, and excessive data permutations.
7. Validate and dry-run the manifest, then ask before applying.Example test
## Upgrade to annual plan
- Open the pricing page.
- Select annual billing.
- Start the Pro plan checkout.
- Verify the checkout page shows the Pro annual plan.After migration
- Review the created tests in the Smoketest dashboard.
- Run each migrated test and compare the recording with the original journey.
- Replace scheduled Mabl plans with Smoketest schedules, GitHub triggers, or deployment webhooks once the runs are stable.