Autonomy Docs
Migrate

Selenium

Convert Selenium WebDriver suites in Java, Python, C#, or JavaScript to Autonomy test cases. Retire the page objects and explicit waits.

Selenium suites span languages, but the structure is always the same: a driver, locators, explicit waits, and page objects. Migration is language-agnostic because the agent reads the intent, not the bindings.

Prompt

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

Codetext
Migrate the Selenium 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 page-object methods into the steps that call them; the page object's locator strategy is discarded. 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

  • By.id / By.xpath / By.cssSelector become described targets.
  • WebDriverWait / ExpectedConditions are dropped.
  • driver.get() becomes Navigate; sendKeys becomes Type; getText() feeding an assertion becomes Assert.
  • Grid / capabilities configuration becomes Test Case platform selection.

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

On this page