From Selenium and Appium

​

Before and after

@Test
public void guestCanBuyBlanket() {
  WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
  driver.get("https://shop.example.com/products/42");
  wait.until(ExpectedConditions.elementToBeClickable(
      By.cssSelector("[data-testid='add-to-cart']"))).click();
  driver.findElement(By.id("cart-icon")).click();
  wait.until(ExpectedConditions.textToBePresentInElementLocated(
      By.cssSelector(".cart-items"), "Gravity Blanket"));
  driver.findElement(By.xpath("//button[contains(.,'Checkout')]")).click();
  WebElement email = wait.until(ExpectedConditions.visibilityOfElementLocated(
      By.name("email")));
  email.sendKeys("jeff@example.com");
  driver.findElement(By.cssSelector("button[type='submit']")).click();
  wait.until(ExpectedConditions.urlMatches("/orders/\\w+"));
  Assert.assertTrue(
      driver.findElement(By.tagName("body")).getText().contains("Order confirmed"));
}

fileType: momentic/test/v2
id: guest-checkout
url: https://shop.example.com/products/42
steps:
  - click: Add to cart
  - click: the cart icon
  - assert: The cart lists "Gravity Blanket"
  - click: Checkout
  - type:
      text: jeff@example.com
      into: the Email field
  - click: Place order
  - waitForUrl:
      regex: /\/orders\/\w+/
  - assert: An order confirmation is visible

​

API mapping

​

Page objects and helpers

fileType: momentic/module/v2
id: log-in
name: Log in
parameters:
  - name: USERNAME
  - name: PASSWORD
steps:
  - type:
      text: "{{ env.USERNAME }}"
      into: the Username field
  - type:
      text: "{{ env.PASSWORD }}"
      into: the Password field
  - click: the Submit button

​

What keeps working unchanged

• Your test data and seed APIs. javascript steps run Node with axios, pg, faker, and child_process. Existing seed endpoints and database helpers port without redesign.
• Appium-specific glue. On mobile, the appium step executes arbitrary mobile: scripts (mobile: shell, mobile: deepLink, gestures that no preset step covers). Port the common paths to natural-language steps and keep appium for the edge cases.
• Your CI. Replace the grid and driver setup with npx momentic install-browsers chromium (web) or a hosted browser/emulator. See Hosted test environments.

​

What does not map

• Driver lifecycle control. There is no WebDriver object to hold or pass. You cannot run two driver sessions in one test; parallel testing is per-test parallelism, not multi-session choreography.
• XPath/CSS depth. Selectors still work as targets, but the intended use is natural language. Complex XPath logic has no equivalent: express the element by what it looks like, and let step caching keep it fast.
• ExpectedConditions variety. Momentic covers the common conditions (visible, text, URL, attribute) but not exotic ones like elementSelectionStateToBe. A javascript step in the browser can check anything the DOM exposes.
• Real devices. Remote execution covers Android emulators and iOS simulators, not physical device farms. Keep a device-farm runner for the tests that need hardware.
• Non-HTTP protocols. Selenium suites that drive WebDriver against non-browser targets do not map; Momentic tests browsers and mobile apps.

​

Incremental strategy

1. Start on the suite’s worst offender: the flakiest flow, the one with the most ExpectedConditions. Port it to a single *.test.yaml and run it daily for a week. This is the fastest way to see whether Momentic’s waiting model holds up on your app.
2. Convert page objects to modules as you go; the second test on the same flow is nearly free.
3. For mobile, run a local emulator first (momentic-mobile run against your .apk/.app), then switch individual tests to remote instances through the Region selector.
4. Run Selenium and Momentic side by side in CI. Label ported tests and gate on them once they stabilize.
5. Retire the grid last: after the browser coverage you need is confirmed, not when the first suite passes.

​

Porting at scale with a coding agent

Port the Selenium tests in src/test/java/checkout/ to Momentic tests.
Read the momentic-test skill first. Write one *.test.yaml per @Test method,
convert each Page class to a *.module.yaml, drop all explicit waits, and keep
any JavascriptExecutor blocks as javascript steps. Run each ported test with
npx momentic run <file>.

​

Related

• Test portability
• Web steps reference
• Mobile steps reference
• Hosted test environments
• Modules