1. Resources
  2. /
  3. Blog
  4. /
  5. Introducing Test Engine Workflows

Introducing Test Engine Workflows

2 minute read

At Buildkite, we’re constantly striving to make your testing faster, smarter, and easier to manage. That’s why we’re excited to announce our latest feature for Test Engine: workflows! This new capability is designed to help teams of all sizes streamline their testing process and maximize productivity, by automatically detecting flaky patterns, surfacing them in Test Engine, and triggering custom responses.

What are Test Engine workflows?

Workflows help developers detect, manage, and act on flaky tests with precision and efficiency. They provide a flexible foundation for creating automated responses to the testing patterns that matter most to your organization.

Here’s what you can configure with workflows:

  • Monitors: Heuristics that detect flaky behavior. Today, Test Engine supports three: transition count, passed on retry, and probabilistic flakiness.
  • Actions: Automated responses that run when a monitor triggers. You can label tests, mute or skip tests, send Slack or webhook notifications, or create issues in Linear.
  • Tag filters: Optional filters to narrow which executions a monitor evaluates (for example, only monitoring results from your main branch or a merge queue branch).

Why it matters

Many teams get bogged down and postpone dealing with flaky tests. The typical response is to retry or ignore these tests to keep their engineering teams unblocked. But neither approach is ideal. 

Some of our more advanced customers have invested in custom solutions to maintain high confidence and streamline testing. Workflows address these common flaky-test pain points by providing more sophisticated detection methods, fine-grained control over how you respond to different types of flaky tests, and customizable actions that connect directly to your team's existing tools and processes.

Ways you can use workflows

  • Catch flaky tests early: Add monitors to surface unreliable tests before they slow down your pipeline.
  • Respond automatically: Configure actions to label tests, quarantine them by changing their state, or notify your team the moment flakiness is detected.
  • Exercise fine-grained control: Tailor how you detect and respond to flaky tests with precision. Create separate workflows for different test types, teams, or environments.

Get started today

Workflows are included in Test Engine and you can try this feature today in public preview. Customers on Pro and Enterprise plans can currently use up to three workflows per suite.

Watch the demo below to learn more or visit the docs.

Happy testing!


Related posts

Start turning complexity into an advantage

Create an account to get started with a 30-day free trial. No credit card required.

Buildkite Pipelines

Platform

  1. Pipelines
  2. Public pipelines
  3. Test Engine
  4. Package Registries
  5. Mobile Delivery Cloud
  6. Pricing

Hosting options

  1. Self-hosted agents
  2. Mac hosted agents
  3. Linux hosted agents

Resources

  1. Docs
  2. Blog
  3. Changelog
  4. Example pipelines
  5. Plugins
  6. Webinars
  7. Case studies
  8. Events
  9. Migration Services
  10. Comparisons

Company

  1. About
  2. Careers
  3. Press
  4. Security
  5. Brand assets
  6. Contact

Solutions

  1. Replace Jenkins
  2. Workflows for AI/ML
  3. Testing at scale
  4. Monorepo mojo
  5. Bazel orchestration

Legal

  1. Terms of Service
  2. Acceptable Use Policy
  3. Privacy Policy
  4. Subprocessors
  5. Service Level Agreement

Support

  1. System status
  2. Forum
© Buildkite Pty Ltd 2025