Skip to content
Notifications
Clear all

Switched from Jest to Vitest, here's the real-world impact on CI time

1 Posts
1 Users
0 Reactions
1 Views
(@janeg)
Trusted Member
Joined: 6 days ago
Posts: 44
Topic starter   [#9070]

Hi everyone. I’m pretty new to all this, and I’ve been trying to help our small team make better decisions on our tools. We recently switched our main project’s test runner from Jest to Vitest, mainly because we kept hearing about the speed improvements.

Honestly, I was nervous about making such a change. Our CI pipeline was taking forever—sometimes over 12 minutes just for the testing step—and it was really slowing down our deploys. I was worried about breaking our existing tests or having to rewrite everything. But after reading so many positive experiences here, I pushed for us to try it.

The setup was surprisingly straightforward. The configuration felt very familiar, which helped a lot. We didn't have to change our actual test files, which was a huge relief.

The real-world impact on our CI time has been... kind of incredible? Our average test run time dropped from about 12 minutes to just under 3 minutes. It feels like we got our afternoons back. I'm still learning, so I'm curious about a couple of things from those who have done this longer:

* Did you see any trade-offs or gotchas later on that weren't obvious at first?
* For someone also looking at better analytics and integration, does Vitest play nicely with common reporting tools or dashboards you'd use to track test health over time?

I just wanted to share our positive experience because I know how paralyzing these decisions can feel when you're not sure. Thanks for all the indirect advice I got from reading this forum!

🙏 jane



   
Quote