| title | Changelog |
|---|---|
| description | Recent updates to Trunk Flaky Tests. |
| rss | true |
<Update label="May 28, 2026" tags={["Flaky Tests"]}> Flaky Tests: Lifecycle & Performance Monitors
Three new monitor types — new-test, skipped-test, and slow-test — apply labels to tests based on lifecycle and performance signals, without affecting health status.
<Update label="May 19, 2026" tags={["Flaky Tests"]}> Flaky Tests: Linear Field Defaults and Link Existing Tickets
Set per-repository defaults for auto-created Linear tickets, and link existing Linear tickets to a test without creating a duplicate.
<Update label="May 18, 2026" tags={["Flaky Tests"]}> Flaky Tests: Failure Count Monitor
Flag tests the moment they accumulate a configured number of failures on monitored branches.
<Update label="May 18, 2026" tags={["Flaky Tests"]}> Flaky Tests: Apply Labels from Monitors
Monitors can now apply labels to tests instead of classifying them as flaky or broken.
<Update label="May 18, 2026" tags={["Flaky Tests"]}> Flaky Tests: Organization-Scoped Test Labels
Tag, organize, and filter your test suite with org-wide labels.
<Update label="April 8, 2026" tags={["Flaky Tests"]}> Flaky Tests: API Token Auth for the Trunk MCP Server
The Trunk MCP server now accepts a Trunk organization API token via the Authorization: Bearer header, so you can use Trunk's MCP tools from CI jobs, scripts, and any client that doesn't support an OAuth flow.
<Update label="March 27, 2026" tags={["Flaky Tests"]}> Flaky Tests: Automatically Create Jira Issues from Webhooks
A new Jira connector in your webhook settings creates issues in your Jira Cloud project whenever a test's status changes to flaky and impacts more than a configurable number of PRs.
<Update label="March 24, 2026" tags={["Flaky Tests"]}> Flaky Tests: Configurable Threshold Monitors with Live Preview
You now have full control over how flaky tests are detected. Threshold monitors let you define exactly when a test should be flagged as flaky or broken, set the failure rate threshold, time window,…
<Update label="February 2, 2026" tags={["Flaky Tests"]}> Flaky Tests: Infrastructure Failure Protection
When infrastructure issues like database outages, network problems, or CI runner failures cause a large number of tests to fail simultaneously, retrying those tests can trigger mass false flaky…
<Update label="November 18, 2025" tags={["Flaky Tests"]}> Flaky Tests: New API endpoints
We’ve added three new endpoints to make it easier to investigate flaky tests, automate triage, and integrate test health into your workflows.
<Update label="September 9, 2025" tags={["Flaky Tests"]}> Flaky Test: Corrected CLI test failure reporting flag
Resolved an issue where test failures were not being reported or displayed when using the --disable-quarantining flag.
<Update label="September 9, 2025" tags={["Flaky Tests"]}> Flaky Tests: Auto quarantine no longer applied to broken tests
Auto-quarantining test cases have been updated to target only 'flaky' tests specifically. Previously, both 'flaky' and 'broken' tests were subject to automatic quarantine.
<Update label="August 25, 2025" tags={["Flaky Tests"]}> Flaky Tests: New endpoint and XCode 26 support
A new endpoint is available from the trunk api at /flaky-tests/list-unhealthy-tests for your CI/CD integrations.
<Update label="July 2, 2025" tags={["Flaky Tests"]}> Flaky Tests: Commit details in timeline
We’ve added additional details about commits that trigger test status changes to test timelines in the Flaky Tests dashboard.
<Update label="June 25, 2025" tags={["Flaky Tests"]}> Flaky Tests: Manual test status overrides
You can now manually set a test’s status to Flaky, Healthy, or Broken in the Flaky Tests dashboard.
<Update label="June 18, 2025" tags={["Flaky Tests"]}> Flaky Tests: Test suite and class available on test details page
The names of a test’s suite and class are now visible on the test details page of the flaky test dashboard, along with a file search link for repos using either GitHub or Bitbucket as source control…
<Update label="June 11, 2025" tags={["Flaky Tests"]}> Flaky Tests: test_case.quarantining_setting_changed webhook
We’re happy to announce that a new testcase.quarantiningsetting_changed webhook is now available for all Flaky Tests users.
<Update label="May 21, 2025" tags={["Flaky Tests"]}> Flaky Tests: Improved test failure details
More changes have landed on the Flaky Tests dashboard: unique failure details on the test details page are now available in a single table view.
<Update label="May 15, 2025" tags={["Flaky Tests"]}> RSpec Plugin for Ruby repos
The new Flaky Tests RSpec plugin is the best way to run RSpec tests and upload the results to Trunk.
<Update label="April 25, 2025" tags={["Flaky Tests"]}> Flaky Tests: Linear integration
We now have a built-in Linear integration that creates tickets with relevant test and failure information from your flaky tests.
<Update label="April 25, 2025" tags={["Flaky Tests"]}> Flaky Tests: Link Ticket to Test Case API
Today, we’re introducing a new Link Ticket to Test Case API that allows you to link your existing Linear or Jira tickets to tests in the Flaky Tests dashboard.
<Update label="April 17, 2025" tags={["Flaky Tests"]}> Flaky Tests: Track environment-specific flakes with variants
Starting today, the --variant option should be used to upload test results when the same tests are run on different environments, also known as matrix builds.
<Update label="April 9, 2025" tags={["Flaky Tests"]}> Flaky Tests: Test detail dashboard UI improvements
The test details page in the Flaky Tests dashboard is getting a major UX overhaul.
<Update label="March 26, 2025" tags={["Flaky Tests"]}> Flaky Tests: Quarantined Tests API
A new Quarantined Tests API is now available to all Flaky Tests users. This API fetches a list of currently quarantined tests for a given repo, allowing organizations to implement custom workflows to…
<Update label="February 26, 2025" tags={["Flaky Tests"]}> Flaky Tests: Detailed Jira integration status updates
We have an exciting update for teams using the Flaky Test Jira integration to create and track their tickets.
<Update label="February 14, 2025" tags={["Flaky Tests"]}> Flaky Tests: Set a custom stable branch
If your stable branch is not main, you can now set a custom stable branch for your repositories to improve flaky test detection.
<Update label="February 10, 2025" tags={["Flaky Tests"]}> Flaky Tests: Weekly reports
We're excited to introduce a new way to help your team stay on top of your repository's test health through weekly email reports.
<Update label="January 29, 2025" tags={["Flaky Tests"]}> Flaky Tests: Webhook Integration for Slack, Microsoft Teams, GitHub Issues, and Linear
We're excited to introduce webhook integrations for Slack, Microsoft Teams, GitHub Issues, and Linear.
<Update label="January 16, 2025" tags={["Flaky Tests"]}> Flaky Tests: CODEOWNERS support
We’re thrilled to announce support for CODEOWNERS in our Flaky Tests product, which is available for both GitHub and GitLab repositories.
<Update label="January 14, 2025" tags={["Flaky Tests"]}> Flaky Tests: Support for Bazel build event protocol
Trunk Flaky Tests now supports uploading test results by parsing Bazel Build Event Protocol (BEP) files.
<Update label="January 3, 2025" tags={["Flaky Tests"]}> Flaky Tests: Flaky test detection on merge branches
We’re excited to announce improved flaky test detection for merge queue users. In a merge queue, a single flaky failure will force every enqueued PR behind it to be retested, affecting every engineer…
<Update label="December 16, 2024" tags={["Flaky Tests"]}> Flaky Tests: Webhooks for status changes
We’re excited to announce the addition of webhooks for flaky tests, designed to help you automate your workflows for better handling of flaky tests.
<Update label="November 12, 2024" tags={["Flaky Tests"]}> Flaky Tests: New onboarding flow
Hi everyone, we’ve introduced a new onboarding flow to make it easier to integrate your test framework and CI provider with Trunk.
<Update label="November 11, 2024" tags={["Flaky Tests"]}> Flaky Tests: Added Flaky Test commands to Trunk CLI
The Trunk CLI now includes commands for uploading and validating test results for Trunk Flaky Tests.
<Update label="November 8, 2024" tags={["Flaky Tests"]}> Flaky Tests: Dashboard improvements
We’re continually refining our UX with the help of our beta users’ feedback and we’ve made some changes to how Flaky Tests displays key information on the dashboards.
<Update label="November 4, 2024" tags={["Flaky Tests"]}> Flaky Tests: Data uploads view
A common pain point during onboarding is the lack of transparency after the Trunk CLI uploads test results.
<Update label="October 28, 2024" tags={["Flaky Tests"]}> Flaky Tests: Improved support for iOS and Swift developers
Flaky Tests now supports the XCResults format outputted by Swift projects using XCTests. You can now upload the .xcresults format to Trunk directly, without configuring a JUnit XML reporter.
<Update label="October 17, 2024" tags={["Flaky Tests"]}> Flaky Tests: PR test summaries
We're excited to introduce a powerful new feature that will help you accelerate your PR iterations: PR Test Summaries!
<Update label="October 14, 2024" tags={["Flaky Tests"]}> Flaky Tests: Quarantining
We’re excited to provide a new way for you to mitigate the negative impact of flaky tests in your repo through quarantining.
<Update label="August 27, 2024" tags={["Flaky Tests"]}> Flaky Tests: Jira Integration
We’re excited to announce the latest enhancement: Jira integration for managing flaky tests. This update builds on our MVP by streamlining the issue management process within Jira.
<Update label="July 15, 2024" tags={["Flaky Tests"]}> Flaky Tests: Issue handling MVP
Today, we are releasing our first feature to support issue handling related to flaky tests. This MVP feature is designed to streamline reporting and managing flaky tests, saving valuable time and…
<Update label="June 28, 2024" tags={["Flaky Tests"]}> Flaky Tests: UX improvements
We are rolling out substantial UX improvements to the dashboard and detail views. These enhancements provide users with quick and easy access to critical information.