Skip to content
Source: StarSling

⚡StarSling Cuts Mastra's Test Suite From 30 Minutes to 5

Your CI pipeline might be costing more than you think

TL;DR

Three teams cut their CI and test times dramatically using StarSling. Mastra dropped its test suite from nearly 30 minutes to just over 5, while Partcl's queue time fell from 9.5 minutes to 35 seconds. If your reviews and CI are slow, this is worth a look.

Mastra's test suite used to take 29 minutes and 56 seconds. After switching to StarSling, it runs in 5 minutes and 6 seconds. That's roughly six times faster, and the team says the real win was seeing how much time reviews and CI were quietly eating. If you're shipping code daily, slow CI is a tax on every PR. Better Auth cut its end-to-end testing from 2 minutes and 22 seconds to 1 minute and 4 seconds, and saved what they describe as countless hours of CI time. Partcl's agents were opening pull requests within a day of moving to StarSling Runners, which says something about how much queue time was blocking automation. The numbers are striking: Mastra went from 29:56 to 5:06, Better Auth from 2:22 to 1:04, and Partcl's queue from 9.5 minutes to 35 seconds. Partcl's Rust CI tests also ran twice as fast. These are vendor-reported results from three customers, so run your own benchmarks before drawing conclusions for your stack.

StarSling Cuts Mastra's Test Suite From 30 Minutes to 5 — StarSling

Key Points

1

Mastra's test suite dropped from 29 minutes and 56 seconds to 5 minutes and 6 seconds after adopting StarSling, roughly a six-fold improvement in total test runtime for the project.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

CI/CDtestingStarSlingdeveloper-productivityrunners

Comments

Subscribe to join the conversation...

Be the first to comment