Engineers Own QA with Momentic

Diving deeper into

Wei-Wei Wu, CEO of Momentic, on AI-native end-to-end testing

Interview
They don't have separate QA organizations—engineering owns QA.
Analyzed 5 sources

This is really a statement about where software testing spend and responsibility are moving. When engineers own quality, testing stops being a handoff at the end of the release cycle and becomes a blocking check inside the normal build, review, and deploy workflow. That favors tools like Momentic, which plug into GitHub, run locally and in CI, and let the same person who ships a feature also create and maintain the test for it.

  • The operational logic is simple. Traditional QA creates a queue. Engineers build a feature, then wait for someone else to click through it, reproduce bugs, and send feedback back upstream. Momentic is built for a different loop, where the engineer records or writes a test, checks it into GitHub, and runs it as a pull request gate before merge.
  • This matches broader DevOps research. DORA finds better outcomes when developers are primarily responsible for creating and maintaining automated tests, and when acceptance test failures are easy for developers to fix. The gain is faster feedback and less context switching, not just lower headcount for a QA department.
  • It also explains the split between newer testing vendors. Momentic is a self serve developer tool for engineering led teams. QA Wolf is a managed service for companies that still want an outside team to create coverage, investigate failures, and own much of the testing work for them. The product choice often follows the org design choice.

The next wave of testing products will be shaped less by who can write test scripts, and more by who can fit cleanly into an engineer owned delivery loop. As AI coding increases release volume, the winning tools will be the ones that turn testing into an automatic part of shipping, not a separate function downstream.