Skip to content

From Selenium

Convert Selenium WebDriver suites into Smoketest tests.

View as Markdown

Selenium suites usually include page objects, waits, driver setup, Grid configuration, and locators spread across several languages. Much of that code exists to control the browser at a low level.

Smoketest starts one level higher: describe the journey and let the agent operate the browser.

Translate the concepts

SeleniumSmoketest
Test method in JUnit, TestNG, pytest, NUnit, RSpec, or MochaOne test
Test class or suiteTest naming, tags, or project grouping
driver.get()Start URL or navigation step
findElement(...).click() / sendKeys()Action step in words
Framework assertion on page stateVerification step in words
Page object methodUseful source text for the test step
Login helperLogin sharedStep or environment-backed login steps
Grid and driver binariesManaged browser execution in Smoketest

What to migrate

Page object method names are often the best migration input. A method like billingPage.downloadLatestInvoice() usually describes exactly what the Smoketest test should say.

Keep browser-driver infrastructure, cross-browser implementation checks, API setup/teardown hooks, and utility tests outside Smoketest. Seed staging data before the run or use stable test accounts.

Quick migration prompt

Text
Use $smoketest-explore to migrate this repository's Selenium WebDriver end-to-end suite to Smoketest.

1. Check Smoketest CLI install and auth first.
2. Find Selenium test files and page object classes.
3. Identify base URLs from config, properties, env vars, or driver.get calls.
4. Convert each real user journey into one .smoketest/explore test draft.
5. Use page object method names to recover user intent.
6. Drop locators, waits, driver setup, Grid setup, and retry wrappers.
7. Store login credentials in Smoketest environments.
8. Validate and dry-run the manifest, then ask before applying.

Example test

Markdown
## Download latest invoice

- Open billing settings.
- Find the invoice history.
- Download the latest invoice.
- Verify the invoice download action completes successfully.

After migration

  • Start with your highest-value smoke suite rather than every historical WebDriver test.
  • Review failures with screenshots and recordings in the run history.
  • Keep Selenium around until migrated tests are green on the same staging environment.

On this page