Migrating from Playwright, Cypress and Cucumber

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

Point sdods analyze <dir> --apply at the existing suite. It copies the specs into projects/<slug>/recorded/imported/ and they run as the recorded layer immediately. Pass --no-import-specs to scaffold the project without copying them.
Move base URLs and credentials into envs/<env>.yaml and .env.<env>.
Convert high-value flows with sdods record convert <spec> so they become tagged features with shared steps.
Turn page.locator('css') calls into heal.locator(primary, context) in page objects as you touch them.

Run sdods analyze to detect routes, the test-id attribute (data-cy is recognised) and existing specs.
Port custom commands to steps in the shared vocabulary or to page-object methods.
Replace cy.intercept fixtures with the mock step or HAR files.
Keep data-cy as testIdAttribute so locators keep working.

Copy .feature files into features/<module>/; add the layer and suite tags; sdods lint --fix-tags handles obvious folders.
Map step definitions: most HTTP and navigation steps already exist in the shared library; keep the rest in steps/*.steps.ts using the project test from steps/fixtures.ts.
Replace world state with the apiContext variables and dataset rows.
Replace separate UI and API runners with one sdods run.

Do the migration per module and let the coverage report show what is still uncovered.