Buildkite Test Engine

Scale out your testing across any framework with Buildkite Test Engine. Speed up builds with real-time flaky test management and intelligent test splitting. Drive accountability and get more out of your existing CI compute with performance insights and analytics.

Where Buildkite Pipelines helps you automate your CI/CD pipelines, Test Engine helps you track and analyze the steps in these pipelines, by:

  • Shipping code to production faster through test optimization.
  • Working directly with Buildkite Pipelines, as well as other CI/CD applications.
  • Identifying, fixing, and monitoring test performance.
  • Tracking, improving, and monitoring test reliability.
Screenshot of test suite trend showing five metrics over 28 days

Buildkite Test Engine was previously called Buildkite Test Analytics.

Get started

Run through the Getting started tutorial for a step-by-step guide on how to use Buildkite Test Engine.

If you're familiar with the basics, begin configuring test collection for your development project. Do this by setting it up with the required Buildkite test collectors for your project's testing frameworks (also known as test runners), which sends the required test data information to Test Engine:

:rspec: RSpec :ruby: minitest :jest: Jest :mocha: Mocha :cypress: Cypress :jasmine: Jasmine :playwright: Playwright :swift: Swift :android: Android :pytest: pytest :golang: Go :junit: JUnit :dotnet: .NET :elixir: Elixir :rust: Rust

If a Buildkite test collector is not available for one of these test runners, you can use other test collection mechanisms instead.

Once test collection has been set up in your development project, you can proceed to run your tests, and analyze and report on them through its test suites. Learn more about this from the Test suites overview page, which covers Test Engine's concepts and functionality.

Core features

Data retention

The data uploaded to Test Engine is stored in S3 and deleted after six months.