Momentic Product and use-case questions Flashcards
(56 cards)
Do you have customers with >3,000 UI tests?
Webflow has over 10,000 UI tests
Do you have customers with >300,000 test executions per month?
Notion executes >200,000 tests per day as part of CI/CD on every commit
Can you support >2,500 test executions in a 15-minute period from a single customer?
At peak, Notion executes >10,000 tests in a 15-minute period as part of CI/CD on every commit
Can you support >10,000 test executions in a 15-minute period from a single customer?
At peak, Notion executes >10,000 tests in a 15-minute period as part of CI/CD on every commit
Do your customers who already have automed UI tests see a significant boost in productivity? Provide a % productivity boost from a customer with previously automated UI tests and how you calculated this in the comments.
Notion migrated from Selenium and saw a 70% decrease in time to automate, 30% decrease in execution time, and 99% decrease in test flakiness. This is self-reported from the customer using their Datadog dashboards and analytics.
Do your customers who already have automated UI tests see significant cost savings when moving over from previous systems / products? Provide a % cost savings from a customer with previously automated UI tests and how you calculated this in the comments.
Yes. Customers with previously automated UI tests have seen dramatic cost savings after switching, largely due to improvements in test reliability and reductions in maintenance and debugging time.
For Customer 1, moving from Cypress to Momentic, savings were calculated at approximately 98.7% reduction in engineering costs associated with addressing flaky tests (from $225,000/month to $975/month). This was based on total number of executions, the percentage of tests that were flaky, the debugging time required per failure, and the hourly engineering rate.
Calculation example (Customer 1):
Before: 150 tests, 3% failure rate, 50 executions/day
225 failed tests/day × 30 days = 6,750 failed tests/month
30 min to resolve each = 3,375 engineer-hours/month
At $100/hr = $337,500/month on flaky test maintenance
After: Failure rate drops to 0.65%
0.975 failed tests/day × 30 days = 29.25/month
29.25 × 30 min = 14.625 engineer-hours/month
$1,462.50/month on maintenance
Cost savings: ($337,500 - $1,462.50)/$337,500 ≈ 99.6% cost savings on flaky test maintenance
Even accounting for variations in engineer cost, execution volume, or failure rates, customers consistently report 60–99% cost savings post-migration, especially in time spent maintaining and debugging tests.
Do you support no code / low code options for creating automated UI tests?
Yes. Momentic’s tests are all completely built using our low-code editor. Test definitions in Momentic are all in natural language. If you can describe the scenario to a manual tester, you can automate it in Momentic.
https://momentic.ai/docs/editor/test-definition
Do you support porting over existing UI tests written in python?
Yes. Momentic supports importing any tests in any language. Momentic translates imported tests using codebase context into natural language test plans and then automatically generates Momentic tests.
Is the average rework time of a ported UI test <10 minutes per test? Put the average time in the comments section.
The average time to port a UI test depends on the complexity of the test.
However, Notion was able to migrate 200 Selenium tests into Momentic with an average time of 6 minutes per test.
Can you upload tests in Google Docs or PDF format?
Yes. Momentic’s test generation ingests text and turns them into working Momentic tests.
(Google docs or PDF) Dev Designs
Yes. Momentic’s test generation ingests text and turns them into working Momentic tests.
(Figma) UX Mocks
No. Figma UX mocks do not include enough information to accurately determine user flows under test.
Do you support self-healing tests that can adapt to UI / selector changes?
Yes. Momentic tests are defined in natural language. This means that they are not tied to hardcoded attributes like XPath or CSS selectors. As long as there is an element on the page that matches the input description, our AI will find it and adapt.
For larger user flow changes, Momentic is able to make edits to tests as part of the Failure recovery process. These changes will require human approval to be accepted.
https://momentic.ai/docs/prompting/finding-elements
https://momentic.ai/docs/failure-recovery
Do you support an audit log of changes made by the self-healing features?
Yes. Every test execution has a corresponding test trace. We surface information such as targeted element, AI thoughts, screenshots, HTML & a11y snapshots to users to share how self-healing was done.
Do you support the ability to review and approve the changes made by the self-healing features?
Yes. Every test execution has a corresponding test trace. Proposed changes made by Momentic’s AI as part of Failure recovery will show up as a diff that needs to be reviewed by a human and accepted.
https://momentic.ai/docs/failure-recovery
Do you support strictly defined asserts?
Yes. Momentic supports a variety of different assertions. We support JavaScript assertions, element-based assertions, page content assertions, as well as multi-modal AI assertions.
https://momentic.ai/docs/prompting/writing-assertions
Do you support fuzzy asserts (for testing AI features)?
Yes. Fuzzy assertions are supported through multi-modal AI assertions.
Quora uses Momentic to test poe.com which is an AI chatbot platform. They use AI assertions to assert on dynamically generated content and whether it is correct and on topic.
Do you support reusable steps / setup (i.e. steps to log in)?
Yes. Momentic supports reusable steps through modules. Modules are shared steps that can be parameterized just like functions. You can use modules to share and reuse common logic like log in.
https://momentic.ai/docs/organization/modules
Do you support the ability to see and modify the code behind the human readable test case steps?
Yes. Momentic’s natural language test cases serialize to YAML files which are human readable and reviewable.
https://github.com/momentic-ai/examples/blob/main/single-project/create-react-app-test.test.yaml
Do you support multiple browsers? Include in the comments which browsers you support.
Yes. We currently support Chrome, Chromium and Chrome for Testing. We plan on adding support for Safari, Firefox, and Edge in H2 2025.
https://momentic.ai/docs/browsers
Do you support mobile browser sizes? Include in the comments which browser sizes you support or if it is completely customizable.
Yes. We support arbitrary browser sizes that is completely customizable by our customers.
Do you support multiple operating systems? Include in the comments which operating systems you support.
Yes. We support running in multiple operating systems.
Windows 10+, Windows Server 2016+, or Windows Subsystem for Linux (WSL).
macOS 13 Ventura, or macOS 14 Sonoma.
Debian 11, Debian 12, Ubuntu 20.04 or Ubuntu 22.04, Ubuntu 24.04, on x86-64 and arm64 architecture.
Do you support calling API’s as part of test setup?
Yes. Momentic supports sending API calls as a part of test setup.
Do you support calling API’s as part of test assertions?
Yes. Momentic supports sending API calls as a part of test assertions.