Skip to main content

Migrate from Selenium

Teams often leave Selenium when script maintenance, flaky selectors, and developer dependency slow regression. QAlity replaces most UI journey scripts with recorded, editable steps—no Selenium or WebDriver code required.

info

QAlity does not integrate with CI/CD pipelines. Use scheduled test plans in Cloud Execution for recurring regression instead of pipeline hooks.

Migration pathMigration path

1
Pick high-value flows first

Choose 3–5 critical journeys that fail or change most often—for example login, checkout, or account settings. Migrate those before attempting full suite parity.

2
Record each flow in Chrome

Create a test case and use the Recorder while performing the same steps your Selenium test covers. You do not rewrite XPath or CSS by hand at capture time.

3
Review and tighten steps

Open the visual step editor. Remove accidental clicks, add verifications, and fix weak steps. If one element changed, edit or delete that step—or continue recording from the end of the case. You cannot re-record from a mid-case step.

4
Organize into suites and plans

Group related cases into test suites (for example Auth, Checkout). Combine suites into test plans for smoke vs full regression.

5
Enable Auto-Heal

Turn on Auto-Heal so renamed classes, moved buttons, and layout drift are less likely to stop runs. Auto-Heal counts toward your plan’s shared AI action quota.

6
Validate locally, then run in cloud

Run cases with Browser Execution while debugging. Move recurring regression to Cloud Execution for suites and plans.

7
Schedule regression

Set schedules for nightly smoke or pre-release plans. When a scheduled run finishes, Pro and Business can email completion notifications with the report.

What maps from SeleniumWhat maps from Selenium

Selenium ideaIn QAlity
One test method / scriptOne test case
TestNG / JUnit suiteTest suite
Regression suite runnerTest plan + schedule
Parameterized dataCase variations and Data Profile
Base URL per envEnvironments
Screenshots / reportsScreenshots and PDF reports

TipsTips

  • Keep each case focused on one user journey. Long multi-journey Selenium scripts are harder to maintain after migration.
  • Retire Selenium gradually. Keep scripts for edge cases until QAlity coverage is trusted.
  • Compare Execution History and PDFs against former Selenium evidence before cutting over.
Recorder
Capture browser flows without writing scripts.
Auto-Heal
Recover when locators change during a run.
Migrate from Playwright
Move QA-owned flows off code-first specs.
Scheduling test plans
Run plans automatically in the cloud.