Migrate to Smoketest

Smoketest is a good fit for end-to-end user journeys that should run in a real browser and produce a result, live progress, screenshots, and a replayable recording.

When you migrate, do not translate every selector and wait into another kind of selector. Translate the user intent: what page the user starts on, what they do, and what must be true at the end.

Migration workflow

Pick the coverage that represents real user journeys.
Keep unit, component, API-only, scraping, and native-mobile-only tests in their current tools.
Install and sign in to the Smoketest CLI.
Convert each selected journey into one test described in a sentence or two.
Put secrets and test-user values in a Smoketest environment.
Run the migrated tests against staging or preview URLs.
Use recordings and run history to decide what to keep, split, or rewrite.

Quick setup

Shell

npm install --global @smoketest.sh/cli
smoketest auth login
smoketest projects create --name "Production" --url https://staging.example.com --use

If you use Codex or Claude Code, the Smoketest Agent Skills can draft the first pass from your repo:

Shell

codex plugin marketplace add smoketest-sh/skills
codex plugin add smoketest@smoketest

Then ask:

Text

Use $smoketest-explore to read this repo and draft Smoketest tests from the existing browser tests. Check the Smoketest CLI first, store secrets in environments, validate the manifest, and ask before applying.

Choose your source

From Playwright

Convert specs, fixtures, and storage state into browser tests written in words.

From Puppeteer

Turn scripted browser automation into user-intent tests.

From Cypress

Move Cypress end-to-end specs while keeping component tests where they are.

From Selenium

Replace WebDriver page objects and waits with higher-level browser journeys.

From Appium

Move mobile-web and shared web tests; keep native app automation in Appium.

From Maestro

Convert web journeys described in Maestro-style tests into Smoketest tests.

From Mabl

Recreate recorded journeys as editable tests you describe in a sentence.

From Bug0

Bring AI-generated or managed QA test goals into a self-serve Smoketest project.

What Smoketest replaces

Existing test detail	Smoketest equivalent
Browser test file or recorded journey	A test with steps written in words
Shared login helper	A sharedStep or environment-backed login steps
Base URL in config	Project URL, or a run-scoped start URL from CLI/API
Test credentials in env vars	Smoketest environment variables and secrets
CI job running a suite	CLI, API, GitHub triggers, or deployment webhooks
Video and debug artifacts	Run history, screenshots, live view, and recording

What to keep

Smoketest is for browser end-to-end journeys. Keep these in specialized tools:

Unit tests and component tests
API contract tests
Load tests
Scrapers and PDF generation scripts
Native iOS or Android app automation
Very large data-matrix tests where one representative journey is enough for Smoketest

Next steps

Agent Skills

Let a coding agent inspect your repo and draft test files.

CLI

Create, update, run, and watch tests from your terminal.

Environments

Store test-user credentials and staging values safely.