Mabl Engineering Blog
Read post

How We Ship Quality at mabl

mabl's engineering team describes how they scaled their verification layer to match a 4.5x increase in PR throughput (179 to 810 PRs/month) driven by AI coding agents. Their stack includes seven layers from local TypeScript checks to 24/7 production monitoring, using two completely separate mabl stacks (prod and dev) that test each other to avoid shared fate. Key practices include: scoped test routing via Claude skills, automatic Claude Opus PR reviews with on-demand Codex second opinions, an MCP server that feeds deployment test results directly into coding assistants, and treating the test suite as a maintained product with composable flows, flake containment hierarchies, and self-describing plan names. 31% of PRs now flow through agent-only review. The core insight is that at AI-native throughput, the verification layer becomes the system's organizing principle, not a CI detail.

    #testing#cicd#ai-coding
Jun 11•18m read time•From mabl.com
Post cover image
Table of contents
The numbers behind itThe shape of the stackWhy this works (and what's transferable)Why this works (and what's transferable)
6.5K Impressions
Mabl Engineering Blog's image
Mabl Engineering Blog

0 Followers

•

7 Upvotes

Would you recommend this post?

Copy link
WhatsApp
Facebook
X
New Squad
  • © 2026 Daily Dev Ltd.
  • Guidelines
  • Explore
  • Tags
  • Sources
  • Squads
  • Leaderboard