Shifting Tests From Scripts to Intent
Wei-Wei Wu, CEO of Momentic, on AI-native end-to-end testing
This is the key product bet, Momentic is trying to move testing from maintaining scripts to maintaining user intent. Playwright made browser automation far more usable for developers, but teams still check in code that points at page elements and still have to fix that code when the UI shifts. Momentic keeps the test definition in natural language and translates it at runtime, so the maintenance surface moves away from selectors and toward the expected user flow itself.
-
In a Playwright workflow, the asset a team owns is code in its repo. That is powerful because engineers can edit it locally, run it in CI, and reuse it for scraping or automation, but it also means every broken selector becomes engineering cleanup work.
-
Momentic separates the source of truth from the automation layer. Teams define the flow they want, like log in, add item, check out, and the system turns that into granular browser actions at runtime, which is why it argues code generation alone does not solve brittleness.
-
That also explains the competitive split in AI testing. Cypress and Playwright are developer tools for writing scripts. QA Wolf packages testing as a service. Momentic is positioning as software that lets engineering own the workflow without inheriting the same long term script maintenance burden.
If this model works, testing expands from a niche owned by QA specialists into a standard part of shipping code. The winning platforms will look less like script runners and more like reliability systems for every critical product flow across web, API, mobile, and production monitoring.