Maeris logo
Get started for free

Import Existing Tests

If you already have a test suite written in Playwright, Cypress, or Selenium, you can import it directly into Maeris MCP. Imported tests are converted into Maeris test cases, which can then be run, auto-fixed, and synced to the Maeris Portal.

Importing a Test File

To import tests from a file, run:

maeris test import <file>

For example:

# Import a Playwright test file maeris test import tests/auth.spec.ts # Import a Cypress spec file maeris test import cypress/e2e/login.cy.js # Import a Selenium Python test maeris test import test_login.py

Maeris auto-detects the framework from the file contents and applies the appropriate parser. You can also import an entire directory:

maeris test import tests/

Supported Formats

  • Playwright (.spec.ts, .spec.js, .test.ts) — Full support including page fixtures, locators, and expect assertions
  • Cypress (.cy.js, .cy.ts) — cy.get(), cy.contains(), cy.type(), cy.click() commands are mapped to Playwright equivalents
  • Selenium (Python) (.py) — find_element(), click(), send_keys() calls are translated into Playwright actions
  • Selenium (Java) (.java) — Basic WebDriver commands are supported (experimental)
  • Maeris JSON (.json) — Native Maeris test case format exported from the portal

What Gets Imported

During import, Maeris parses and stores the following from your existing tests:

Test Cases

Each test() or it() block becomes a named Maeris test case. The test description is used as the test case name.

Test Steps

Each action within a test (navigate, click, fill, select, wait) is stored as an individual step. Steps are displayed in the Maeris Portal and can be edited after import.

Selectors

CSS selectors, XPath expressions, and data-testid attributes are preserved exactly as written. After import, you can run the auto-fix loop to update any selectors that no longer match your current UI.

Import with Folder Assignment

To import tests and organize them into a specific folder within Maeris:

maeris test import tests/auth.spec.ts --folder Authentication maeris test import tests/checkout.spec.ts --folder "Checkout Flow"

Verifying the Import

After the import completes, list your tests to confirm they were created:

maeris test list

You can also view the details of a specific imported test to verify its steps were parsed correctly:

maeris test get <test-name>

Known Limitations

  • Custom Cypress commands (Cypress.Commands.add) are imported as-is and may need manual adjustment
  • Selenium Page Object Model classes are partially supported — actions within page methods are imported but the class structure is flattened
  • Tests using non-standard async patterns (callbacks instead of async/await) may require manual review after import

Next Steps

After importing your tests, run them with the auto-fix loop to repair any selectors that have drifted from your current UI. See the Run & Auto-Fix Tests guide to get started.