diff --git a/changelog/2026-04-22-flaky-tests-test-collections.mdx b/changelog/2026-04-22-flaky-tests-test-collections.mdx new file mode 100644 index 00000000..dfde3715 --- /dev/null +++ b/changelog/2026-04-22-flaky-tests-test-collections.mdx @@ -0,0 +1,22 @@ +--- +title: "Flaky Tests: Test Collections" +description: "Group tests from a repository into named collections with their own views and quarantine settings." +date: 2026-04-22 +category: Flaky Tests +type: new-feature +--- + +**Test Collections let you organize tests from a repository into named groups, each with its own views, settings, and quarantine policy.** + +A collection is a named group of tests within a repository. Create one from **Flaky Tests > Collections**, then upload results to it by passing its short ID to the Trunk CLI: + +```bash +trunk flakytests upload --test-collection-short-id ... +``` + +Tests, uploads, and configuration are all scoped to the collection across the Flaky Tests app. + +- **Create, edit, and delete collections** — organization admins manage collections from the Flaky Tests app; all members can view them and the tests inside. +- **Collection-level quarantining** — each collection has its own quarantine settings that override the repository defaults, so a critical collection can quarantine aggressively while another never auto-quarantines. + +[Read the docs](https://docs.trunk.io/flaky-tests/get-started/test-collections) to learn more. diff --git a/changelog/index.mdx b/changelog/index.mdx index 05e887db..ab3f2266 100644 --- a/changelog/index.mdx +++ b/changelog/index.mdx @@ -58,6 +58,12 @@ rss: true The Trunk Chrome Extension brings merge queue controls directly into your GitHub pull request page. + + **[Flaky Tests: Test Collections](/changelog/2026-04-22-flaky-tests-test-collections)** + + Group tests from a repository into named collections with their own views, settings, and quarantine policy. + + **[Merge Queue: Drill Down Into Merge Metrics](/changelog/2026-04-21-merge-queue-drill-down-into-merge-metrics)** diff --git a/docs.json b/docs.json index 763b83c9..871ef99e 100644 --- a/docs.json +++ b/docs.json @@ -238,7 +238,8 @@ "flaky-tests/get-started/ci-providers/otherci" ] }, - "flaky-tests/get-started/multiple-repositories" + "flaky-tests/get-started/multiple-repositories", + "flaky-tests/get-started/test-collections" ] }, { @@ -623,6 +624,7 @@ "changelog/2026-05-18-flaky-tests-monitor-label-actions", "changelog/2026-05-18-flaky-tests-test-labels", "changelog/2026-04-30-merge-queue-chrome-extension", + "changelog/2026-04-22-flaky-tests-test-collections", "changelog/2026-04-21-merge-queue-drill-down-into-merge-metrics", "changelog/2026-04-13-merge-queue-terraform-provider", "changelog/2026-03-27-flaky-tests-automatically-create-jira-issues-from-webhooks", diff --git a/flaky-tests/changelog.mdx b/flaky-tests/changelog.mdx index fcd22bd9..3f3c4a91 100644 --- a/flaky-tests/changelog.mdx +++ b/flaky-tests/changelog.mdx @@ -38,6 +38,14 @@ rss: true Tag, organize, and filter your test suite with org-wide labels. +### April 2026 + + + **[Flaky Tests: Test Collections](/changelog/2026-04-22-flaky-tests-test-collections)** + + Group tests from a repository into named collections with their own views, settings, and quarantine policy. + + ### March 2026 diff --git a/flaky-tests/get-started/test-collections.mdx b/flaky-tests/get-started/test-collections.mdx index 342a15d2..764dd4dc 100644 --- a/flaky-tests/get-started/test-collections.mdx +++ b/flaky-tests/get-started/test-collections.mdx @@ -1,7 +1,6 @@ --- title: "Test Collections" description: "Organize your flaky tests into named collections to track and analyze specific subsets of your test suite." -hidden: true --- Test Collections let you group tests from any repository into named sets. Use collections to focus on a subset of your test suite, such as tests owned by a specific team, tests covering a critical service, or any grouping that matters to your workflow. @@ -29,7 +28,7 @@ https://app.trunk.io//flaky-tests/collections/ Pass the short ID when uploading results using the Trunk CLI: ```bash -trunk flakytests upload --collection ... +trunk flakytests upload --test-collection-short-id ... ``` See the [Uploader reference](../reference/cli-reference) for full upload options. @@ -38,8 +37,6 @@ See the [Uploader reference](../reference/cli-reference) for full upload options Once tests are uploaded to a collection, the **Tests** and **Uploads** tabs become active on the collection detail page. -* **Tests** tab: Shows all tests associated with this collection, with their flaky status, failure rates, and labels. -* **Uploads** tab: Shows the history of test uploads sent to this collection. * **Overview** tab: Shows setup instructions and the upload configuration for this collection. * **Tests** tab: Shows all tests associated with this collection, with their flaky status, failure rates, and labels. * **Uploads** tab: Shows the history of test uploads sent to this collection. @@ -63,6 +60,12 @@ Only organization admins can delete collections. Deleting a collection removes it from the **Collections** list. Test data uploaded to the collection is not deleted from your overall test suite. +## Collection-level quarantining + +Each collection has its own quarantining settings that override the repository-level settings for any uploads routed to that collection. This lets you apply a different quarantine policy to a critical collection than to the rest of your suite — for example, aggressive auto-quarantining for one group and none for another. + +Configure it from the collection's **Settings** > **Quarantining** tab. See [Collection-level quarantining settings](../quarantining/index#collection-level-quarantining-settings) for the available toggles and how the override behaves. + ## Permissions | Action | Admin | Member |