Flaky tests, which fail unpredictably without changes in code or environment, can cause significant delays in development. They disrupt merge queues by blocking valid pull requests, leading to resets, wasted resources, and frustration among developers. Merge queues are designed to streamline the integration process, but flaky tests undermine their efficiency. Tools like Aviator MergeQueue help manage these challenges with features such as parallel testing and early validation. By addressing flaky tests and stabilizing testing environments, teams can ensure smoother workflows and more reliable CI/CD pipelines.
Trunk-based development helps achieve continuous delivery and improve developer experience. But it requires using the right tools and processes.
Many code review processes become bottleneck for the engineering teams. Instead of finding bugs, it hinders progress leading to poor developer experience.
The faster a dev team can make changes and release them to production, the sooner they can deliver value to customers, run experiments, and improve quality
FlexReview is an alternative to Codeowners. It uses reviewer expert score along with availability, workloads and the complexity of code change to determine the right reviewers.
This post explores shift-left principles and suggests that stacked PRs will become increasingly useful.
A brief write-up on how stacked PRs work and why they work well at Aviator.
