Plan Your Migration
Use this page before you choose a vendor-specific migration track. A short inventory helps you decide which existing checks can move first and which webmate workflow should become the target.
Inventory the Current Setup
Collect the details that decide the first migration path:
- tests or manual checks that still run regularly,
- browsers, operating systems, mobile devices, and app packages,
- credentials, project IDs, API keys, and CI variables,
- network needs such as proxies, DNS, or internal application access,
- screenshots, logs, findings, and other evidence that reviewers expect.
Choose the Target Workflow
Map each existing workflow to the closest webmate target:
| Existing workflow | webmate target |
|---|---|
| Manual web check | Browser VM plus Workbench access |
| Manual app check | Mobile device plus Workbench access |
| Selenium browser automation | Remote WebDriver session on the webmate Selenium endpoint |
| Appium automation | Appium session on the webmate Selenium endpoint |
| Playwright web tests | Playwright run with webmate remote Selenium settings |
| Cypress desktop-browser tests | webmate-cypressbridge configuration and bridge binary |
Validate the First Migrated Run
Use one small smoke test or manual check first. Confirm that:
- the webmate endpoint, project, and credentials are correct,
- the requested browser, platform, device, or app is available,
- screenshots, findings, logs, or test artifacts appear where reviewers expect them,
- the run can be repeated from the same local or CI environment,
- occupied devices or browser VMs are released after the check.
Roll Out in Small Groups
Move one stable smoke path first, then migrate larger regression groups after the first result is repeatable. Keep each group tied to a clear target workflow so setup problems stay easy to isolate.