Cypress

Cypress suites usually carry the most framework weight: cy.get chains, cy.intercept aliases, and Cypress.Commands.add helpers. All three disappear in migration; what survives is the journey and its assertions.

Prompt

Paste this into a coding agent connected to the Autonomy MCP server from inside the repository:

Migrate the Cypress tests in this repository to Autonomy.
For each test: read it, then create one Autonomy Test Case with autonomy_test_case_create named after the test title.
Convert selectors into plain-language descriptions of the control. Keep every asserted value exactly as written.
Replace hard-coded credentials with agent-chosen fill values and configuration with environment values.
Inline every custom command from cypress/support into the steps that call it. Treat cy.intercept + cy.wait('@alias') as Validate Network steps. Drop waits, retries, and framework fixtures. List existing Test Cases first and skip any that already cover the journey.
Report a table of source test -> created Test Case ID when done.

Mapping notes

• cy.get('[data-cy=x]').click() becomes a Tap/Click on a described control. The data-cy hook is no longer required by the test.
• cy.intercept() + cy.wait('@alias') become Validate Network.
• cy.session() / cy.login() custom commands become real login steps, or a Precondition when the same session is shared.
• cy.fixture() data becomes literal values when under test, otherwise Environment runtime values.

See the migration overview for the full construct-by-construct mapping.