momentic-test
Installation
Summary
Create, run, and maintain end-to-end tests using AI-driven browser automation with YAML serialization.
- Tests are ordered lists of structured steps executed with Playwright and CDP, supporting interactive clicks/types, multimodal assertions, and goal-based AI actions
- Step metadata (selectors, XPaths, coordinates) is cached by git branch to avoid repeated AI calls; cache can be disabled or refreshed per step when targeting dynamic elements
- Tests and reusable modules serialize to disk as
*.test.yamland*.module.yamlfiles (v2 format supports direct YAML editing; v1 requires MCP CLI) - Test context persists across steps via
envvariables; JavaScript steps run in either NODE (with Momentic helpers, database access, OTP/email) or BROWSER (with DOM access) - Smart waiting up to 5 seconds settles page state before targeting; project defaults in
momentic.config.yamlcan be overridden per test for browser type, viewport, auth, proxy, and timeouts
SKILL.md
Momentic background
Execution model
Momentic is an end-to-end testing framework. Tests are ordered lists of structured steps executed with Playwright and CDP.
- Interactive steps such as clicks and types use AI to resolve natural-language targets into concrete browser actions.
- Assertion steps can use multimodal models to evaluate page state.
- Goal-based AI actions can perform broader tasks such as "checkout with credit card".
Cache and memory
Momentic caches resolved step metadata such as selectors, XPaths, visible text, and coordinates so most runs avoid repeated AI calls. This is critical for speed, but stale cache is a real debugging possibility: a step may hit the wrong element. AI assertions may also use past-result memory to stay consistent across runs; bad memory can explain repeated borderline failures.