Upgrading a 3,000-file test suite from Vitest 4 to 5 cut test-step time by about 18%

·4 views

A team moved its 3,000-file test suite from Vitest 4.1.8 to Vitest 5.0.4 and measured the results in CI. Timing only the test step across six full-suite runs, median time fell from 243 to 200 seconds, roughly 18% faster, close to the 19% the Vitest team published for a similar setup. The team cautions that six samples is too few for a firm conclusion, since the bootstrap interval for the change still includes zero. The migration required small fixes: unawaited resolves assertions now fail, mocks must live at module scope, and coverage counted ?? fallbacks as branches. The team estimates the speedup saves about 8 runner-hours a day, though per-pull-request wall-clock gains are around 2 minutes because browser tests were unchanged. The migration took about half a day, and the team plans a follow-up after a week of main-branch runs.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Store Owner Moves Customer Alerts from Custom App to Telegram for Reliability

A developer who runs an online store describes abandoning a custom-built support app in favor of Telegram for customer notifications. The author argues that self-built ecommerce helpdesk apps often suffer from unreliable push notifications. Delays occur because system push channels batch alerts to conserve battery, and notifications can stop entirely once the app is closed. Ongoing maintenance is also costly, since operating system updates can break push logic. The author contends that Telegram avoids these problems because it is not bound to system push policies and does not merge or rate-limit notifications in the same way.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Explainer Breaks Down AI Agent Architecture Using State Machines and Engineered Loops

A developer reading the book AI Agents: The Definitive Guide shares notes on the first chapter, which frames agents as a language model placed inside a loop of reasoning, acting, and feedback. The author describes how finite state machines and hierarchical state machines can be used to model agent design, with LangGraph representing agents as subgraphs. The post also covers how tools, memory, and checkpoints such as those in LangChain and LangGraph help preserve context and make agent behavior easier to verify. The book's central point is that agents are engineered systems whose safety and usefulness come from well-defined workflows and constraints rather than unlimited autonomy.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Statewave Guide Day 4: Passing the safety test still left product answers failing users

A developer's safety tests showed an AI model avoided wrong or unsupported product claims in a self-built application. Human-style usefulness ratings, produced by a separate model rather than people, found most answers were mediocre, with 14 of 21 judged too technical. Ten features displayed an internal verification sentence directly to users, and all ten were rated too technical. The team concluded that accurate data does not automatically translate into user-friendly language. They added a guidance-compilation layer to decide what users need to hear before rendering the text.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Eight Zoho CRM automation workflows worth setting up

Zoho CRM users who find the platform limited to a contact list may be missing automations they never configured. The article outlines eight options, including assignment rules that distribute records among users, workflow rules that trigger actions on record events, and scheduled reminders. It also covers webhooks and Deluge-based custom functions for connecting to other systems, along with approval processes and multi-step cadences for follow-ups. The author notes that some features depend on edition and that certain triggers may not fire for imported records, advising users to test one automation at a time.

0 comments Read more at DEV Community