Guides
Migrating from Playwright, Cypress and Cucumber
Bring existing suites into AutoMax without rewriting everything on day one.
What you'll learn
What to keep, what to convert, and in which order, when you come from plain Playwright, Cypress or a Cucumber-based framework.
From Playwright
- Copy specs into
projects/<slug>/recorded/(automax import playwright <dir>); they run as therecordedlayer immediately. - Move base URLs and credentials into
envs/<env>.yamland.env.<env>. - Convert high-value flows with
automax record convertso they become tagged features with shared steps. - Turn
page.locator('css')calls intoheal.locator(primary, context)in page objects as you touch them.
From Cypress
- Run
automax analyzeto detect routes, the test-id attribute (data-cyis recognised) and existing specs. - Port custom commands to steps in the shared vocabulary or to page-object methods.
- Replace
cy.interceptfixtures with the mock step or HAR files. - Keep
data-cyastestIdAttributeso locators keep working.
From Cucumber frameworks
- Copy
.featurefiles intofeatures/<module>/; add the layer and suite tags;automax lint --fix-tagshandles obvious folders. - Map step definitions: most HTTP and navigation steps already exist in the shared library; keep the rest in
steps/*.steps.tsusing the projecttestfromsteps/fixtures.ts. - Replace world state with the
apiContextvariables and dataset rows. - Replace separate UI and API runners with one
automax run.
Do the migration per module and let the coverage report show what is still uncovered.