diff --git a/docs.json b/docs.json index ae72d10d..caf77abc 100644 --- a/docs.json +++ b/docs.json @@ -174,6 +174,7 @@ "group": "Overview", "root": "flaky-tests/overview", "pages": [ + "flaky-tests/test-collections", "flaky-tests/dashboard" ] }, @@ -181,6 +182,7 @@ "group": "Getting Started", "root": "flaky-tests/get-started/index", "pages": [ + "flaky-tests/get-started/migrate-to-test-collections", { "group": "Test frameworks", "root": "flaky-tests/get-started/frameworks/index", @@ -2164,10 +2166,6 @@ "source": "/flaky-tests/quarantine-service-availability", "destination": "/flaky-tests/quarantining/quarantine-service-availability" }, - { - "source": "/flaky-tests/test-collections", - "destination": "/flaky-tests/get-started/test-collections" - }, { "source": "/flaky-tests/test-labels", "destination": "/flaky-tests/management/test-labels" diff --git a/flaky-tests/dashboard.mdx b/flaky-tests/dashboard.mdx index 6630bdd2..df5faf12 100644 --- a/flaky-tests/dashboard.mdx +++ b/flaky-tests/dashboard.mdx @@ -11,7 +11,7 @@ Press ⌘ K (macOS) or Ctrl K (Windo ## Collections overview -When you navigate to `//flaky-tests`, you land on your [test collections](./get-started/test-collections). The page exists to answer two questions — what collections have flaky tests, and which are not finished being set up. +When you navigate to `//flaky-tests`, you land on your [test collections](./test-collections). The page exists to answer two questions — what collections have flaky tests, and which are not finished being set up. A list of five test collections, each with its Collection ID, repository count, setup progress, test counts, flaky and broken trends, and a runs-per-day chart. @@ -20,7 +20,7 @@ When you navigate to `//flaky-tests`, you land on your [test collectio | Column | Description | |--------|-------------| -| **ID** | The [Collection ID](./get-started/test-collections#the-collection-id), with a button to copy it. This is the value CI passes to route uploads here. | +| **ID** | The [Collection ID](./test-collections#the-collection-id), with a button to copy it. This is the value CI passes to route uploads here. | | **Repos** | How many repositories have uploaded to this collection | | **Setup** | How many of the collection's setup steps are complete | | **Tests** | Total tracked test cases in the collection (60-day window) | @@ -41,7 +41,7 @@ A quarantine status icon appears next to a collection's name when quarantining i While you are migrating, the repository view stays available behind **Legacy view** on this page. It carries the same columns and the same quarantine icons, per repository rather than per collection. -Active repositories (those with test data in the last 30 days) appear at the top of the list. Repositories with no recent data are collapsed under an **Inactive Repositories** section you can expand. See the [migration guide](./migrate-to-test-collections) for how the two views relate, and [Quarantining](./quarantining/) to configure quarantine settings. +Active repositories (those with test data in the last 30 days) appear at the top of the list. Repositories with no recent data are collapsed under an **Inactive Repositories** section you can expand. See the [migration guide](./get-started/migrate-to-test-collections) for how the two views relate, and [Quarantining](./quarantining/) to configure quarantine settings. ## Collection dashboard diff --git a/flaky-tests/detection/pass-on-retry-monitor.mdx b/flaky-tests/detection/pass-on-retry-monitor.mdx index 519bc042..d84a7a9a 100644 --- a/flaky-tests/detection/pass-on-retry-monitor.mdx +++ b/flaky-tests/detection/pass-on-retry-monitor.mdx @@ -49,7 +49,7 @@ You can create more than one pass-on-retry monitor for the same repository. Each A common pattern is to run one monitor scoped to stable branches (like `main`) with a shorter recovery period for fast feedback, and a second monitor scoped to `release/*` branches with a longer recovery period for builds where intermittent failures are more expensive to re-investigate. -To add a monitor, open the **Monitors** tab — on a [test collection](/flaky-tests/get-started/test-collections) or on a repository — and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted. +To add a monitor, open the **Monitors** tab — on a [test collection](/flaky-tests/test-collections) or on a repository — and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted. The repository Monitors tab showing a pass-on-retry monitor, two failure-rate monitors, and lifecycle monitors, each as a separate row with an Add Monitor control. diff --git a/flaky-tests/get-started/ci-providers/otherci.mdx b/flaky-tests/get-started/ci-providers/otherci.mdx index 613502ae..41e12efd 100644 --- a/flaky-tests/get-started/ci-providers/otherci.mdx +++ b/flaky-tests/get-started/ci-providers/otherci.mdx @@ -40,7 +40,7 @@ You can find your token under **Settings** → **Organization** → **General**, Store the Trunk slug and API token obtained in the previous step in your CI provider as a secret, environment variable, or an equivalent concept and name them `TRUNK_ORG_URL_SLUG` and `TRUNK_API_TOKEN` respectively. -Set `TRUNK_TEST_COLLECTION_ID` as well, to the ID of the [test collection](/flaky-tests/get-started/test-collections) the results belong to. It is not a secret, and it is per job rather than per organization — a job that uploads to a different collection sets a different value. +Set `TRUNK_TEST_COLLECTION_ID` as well, to the ID of the [test collection](/flaky-tests/test-collections) the results belong to. It is not a secret, and it is per job rather than per organization — a job that uploads to a different collection sets a different value. ## Upload to Trunk diff --git a/flaky-tests/get-started/frameworks/behave.mdx b/flaky-tests/get-started/frameworks/behave.mdx index 98b346c1..ed35116f 100644 --- a/flaky-tests/get-started/frameworks/behave.mdx +++ b/flaky-tests/get-started/frameworks/behave.mdx @@ -100,7 +100,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/cypress.mdx b/flaky-tests/get-started/frameworks/cypress.mdx index f609f897..bf214c7d 100644 --- a/flaky-tests/get-started/frameworks/cypress.mdx +++ b/flaky-tests/get-started/frameworks/cypress.mdx @@ -138,7 +138,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/gotestsum.mdx b/flaky-tests/get-started/frameworks/gotestsum.mdx index 33894407..a6490269 100644 --- a/flaky-tests/get-started/frameworks/gotestsum.mdx +++ b/flaky-tests/get-started/frameworks/gotestsum.mdx @@ -119,7 +119,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/gradle.mdx b/flaky-tests/get-started/frameworks/gradle.mdx index 32b48864..ecfbcc77 100644 --- a/flaky-tests/get-started/frameworks/gradle.mdx +++ b/flaky-tests/get-started/frameworks/gradle.mdx @@ -111,7 +111,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/jasmine.mdx b/flaky-tests/get-started/frameworks/jasmine.mdx index 490b50e8..ebe4068e 100644 --- a/flaky-tests/get-started/frameworks/jasmine.mdx +++ b/flaky-tests/get-started/frameworks/jasmine.mdx @@ -124,7 +124,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/jest.mdx b/flaky-tests/get-started/frameworks/jest.mdx index 57526c51..e82d1cbf 100644 --- a/flaky-tests/get-started/frameworks/jest.mdx +++ b/flaky-tests/get-started/frameworks/jest.mdx @@ -137,7 +137,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/karma.mdx b/flaky-tests/get-started/frameworks/karma.mdx index 9f9b2f5a..97150817 100644 --- a/flaky-tests/get-started/frameworks/karma.mdx +++ b/flaky-tests/get-started/frameworks/karma.mdx @@ -111,7 +111,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/kotest.mdx b/flaky-tests/get-started/frameworks/kotest.mdx index 93fec351..3eb1f5f8 100644 --- a/flaky-tests/get-started/frameworks/kotest.mdx +++ b/flaky-tests/get-started/frameworks/kotest.mdx @@ -181,7 +181,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/maven.mdx b/flaky-tests/get-started/frameworks/maven.mdx index a3e9e9a3..111b9cf9 100644 --- a/flaky-tests/get-started/frameworks/maven.mdx +++ b/flaky-tests/get-started/frameworks/maven.mdx @@ -126,7 +126,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/minitest.mdx b/flaky-tests/get-started/frameworks/minitest.mdx index 5856fc64..62339fc2 100644 --- a/flaky-tests/get-started/frameworks/minitest.mdx +++ b/flaky-tests/get-started/frameworks/minitest.mdx @@ -109,7 +109,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/mocha.mdx b/flaky-tests/get-started/frameworks/mocha.mdx index cc25f0c7..5f702a2d 100644 --- a/flaky-tests/get-started/frameworks/mocha.mdx +++ b/flaky-tests/get-started/frameworks/mocha.mdx @@ -113,7 +113,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/nightwatch.mdx b/flaky-tests/get-started/frameworks/nightwatch.mdx index 93843305..6cabde5c 100644 --- a/flaky-tests/get-started/frameworks/nightwatch.mdx +++ b/flaky-tests/get-started/frameworks/nightwatch.mdx @@ -111,7 +111,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/nunit.mdx b/flaky-tests/get-started/frameworks/nunit.mdx index 8d34250c..1f2ecf85 100644 --- a/flaky-tests/get-started/frameworks/nunit.mdx +++ b/flaky-tests/get-started/frameworks/nunit.mdx @@ -98,7 +98,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/pest.mdx b/flaky-tests/get-started/frameworks/pest.mdx index 0124f548..1c539421 100644 --- a/flaky-tests/get-started/frameworks/pest.mdx +++ b/flaky-tests/get-started/frameworks/pest.mdx @@ -96,7 +96,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/phpunit.mdx b/flaky-tests/get-started/frameworks/phpunit.mdx index f8d39f9f..68428cef 100644 --- a/flaky-tests/get-started/frameworks/phpunit.mdx +++ b/flaky-tests/get-started/frameworks/phpunit.mdx @@ -96,7 +96,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/playwright.mdx b/flaky-tests/get-started/frameworks/playwright.mdx index 0b343b5b..1b1eb01c 100644 --- a/flaky-tests/get-started/frameworks/playwright.mdx +++ b/flaky-tests/get-started/frameworks/playwright.mdx @@ -120,7 +120,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/pytest.mdx b/flaky-tests/get-started/frameworks/pytest.mdx index 12edd39e..f4add931 100644 --- a/flaky-tests/get-started/frameworks/pytest.mdx +++ b/flaky-tests/get-started/frameworks/pytest.mdx @@ -96,7 +96,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/robot-framework.mdx b/flaky-tests/get-started/frameworks/robot-framework.mdx index 51564ce2..844f22d6 100644 --- a/flaky-tests/get-started/frameworks/robot-framework.mdx +++ b/flaky-tests/get-started/frameworks/robot-framework.mdx @@ -96,7 +96,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/rspec/manual-uploads.mdx b/flaky-tests/get-started/frameworks/rspec/manual-uploads.mdx index 1d72e110..7a0c76db 100644 --- a/flaky-tests/get-started/frameworks/rspec/manual-uploads.mdx +++ b/flaky-tests/get-started/frameworks/rspec/manual-uploads.mdx @@ -106,7 +106,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/swift-testing.mdx b/flaky-tests/get-started/frameworks/swift-testing.mdx index 13656035..d767fb1a 100644 --- a/flaky-tests/get-started/frameworks/swift-testing.mdx +++ b/flaky-tests/get-started/frameworks/swift-testing.mdx @@ -98,7 +98,7 @@ You make an upload to Trunk using the following command: --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/testplan.mdx b/flaky-tests/get-started/frameworks/testplan.mdx index 01d7ec72..a74661fa 100644 --- a/flaky-tests/get-started/frameworks/testplan.mdx +++ b/flaky-tests/get-started/frameworks/testplan.mdx @@ -135,7 +135,7 @@ You make an upload to Trunk using the following command: ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. ## Next Steps diff --git a/flaky-tests/get-started/frameworks/vitest.mdx b/flaky-tests/get-started/frameworks/vitest.mdx index 3722fbb0..841ef9ba 100644 --- a/flaky-tests/get-started/frameworks/vitest.mdx +++ b/flaky-tests/get-started/frameworks/vitest.mdx @@ -155,7 +155,7 @@ curl -fL --retry 3 "https://github.com/trunk-io/analytics-cli/releases/latest/do --token ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/frameworks/xctest.mdx b/flaky-tests/get-started/frameworks/xctest.mdx index 0a388310..05bd6113 100644 --- a/flaky-tests/get-started/frameworks/xctest.mdx +++ b/flaky-tests/get-started/frameworks/xctest.mdx @@ -98,7 +98,7 @@ chmod +x trunk-analytics-cli ``` -You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. +You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues. diff --git a/flaky-tests/get-started/index.mdx b/flaky-tests/get-started/index.mdx index 41fca28f..55997719 100644 --- a/flaky-tests/get-started/index.mdx +++ b/flaky-tests/get-started/index.mdx @@ -40,7 +40,7 @@ Trunk automatically recognizes `main`, `master`, and `develop` as stable branche 1. Push your changes and trigger a CI run 2. Check CI logs for successful upload confirmation -3. Results typically appear within a few minutes. Verify uploads appear at [app.trunk.io](https://app.trunk.io) on your [test collection](./test-collections)'s **Uploads** tab +3. Results typically appear within a few minutes. Verify uploads appear at [app.trunk.io](https://app.trunk.io) on your [test collection](../test-collections)'s **Uploads** tab @@ -49,7 +49,7 @@ Trunk automatically recognizes `main`, `master`, and `develop` as stable branche ### Step 4: Configure flake detection -After uploads are flowing, open your [test collection](./test-collections)'s **Monitors** tab to set up detection. +After uploads are flowing, open your [test collection](../test-collections)'s **Monitors** tab to set up detection. **Pass-on-retry** is enabled by default and is the recommended baseline for everyone. It catches the most common flakiness pattern — a test that fails and then passes on retry within the same commit — without any configuration needed. diff --git a/flaky-tests/migrate-to-test-collections.mdx b/flaky-tests/get-started/migrate-to-test-collections.mdx similarity index 94% rename from flaky-tests/migrate-to-test-collections.mdx rename to flaky-tests/get-started/migrate-to-test-collections.mdx index 0fb7f4e7..5aa70c75 100644 --- a/flaky-tests/migrate-to-test-collections.mdx +++ b/flaky-tests/get-started/migrate-to-test-collections.mdx @@ -2,9 +2,8 @@ title: "Migrate to Test Collections" description: "Move an existing organization from repository-based Flaky Tests to test collections, one CI job at a time." og:title: "Migrating to test collections in Trunk" -hidden: true --- -[Test collections](./get-started/test-collections) replace repositories as the way Flaky Tests is organized. New organizations start on collections. If your organization has been using Flaky Tests already, you will need to gradually migrate to using collections, and both views stay available while you do. +[Test collections](../test-collections) replace repositories as the way Flaky Tests is organized. New organizations start on collections. If your organization has been using Flaky Tests already, you will need to gradually migrate to using collections, and both views stay available while you do. Nothing breaks while you migrate. A CI job that doesn't pass a collection ID keeps uploading exactly as it does today. @@ -45,7 +44,7 @@ That is often what you want. You may wish to create different monitors for each Collections usually map to a team, a service, or a test suite. Group tests you want to configure and review together. -See [Create a collection](./get-started/test-collections#create-a-collection). +See [Create a collection](../test-collections#create-a-collection). @@ -96,7 +95,7 @@ It is one switch for every collection event, not one per event type. What you ar - **You cannot deduplicate on `test_case.id`.** Collection and repository events don't share a test-case ID space, so the same underlying test arrives under two unrelated IDs. `repository.id` is the only handle common to both. - `repository` is omitted rather than guessed when an upload carries no repository. -Leave it off until your consumer is ready and nothing reaches it in the meantime. See [Webhooks](./webhooks/) for the payloads. +Leave it off until your consumer is ready and nothing reaches it in the meantime. See [Webhooks](../webhooks/) for the payloads. ## Dashboards start fresh diff --git a/flaky-tests/get-started/multiple-repositories.mdx b/flaky-tests/get-started/multiple-repositories.mdx index 0bc83e50..fb26e1d8 100644 --- a/flaky-tests/get-started/multiple-repositories.mdx +++ b/flaky-tests/get-started/multiple-repositories.mdx @@ -11,7 +11,7 @@ Three things group tests, and they answer different questions: | Grouping | Use it to | Set by | |---|---|---| -| [Test collection](./test-collections) | Group tests you want to configure and review together — by team, service, or suite — with their own monitors, quarantining, and ticketing. | `--test-collection-id` | +| [Test collection](../test-collections) | Group tests you want to configure and review together — by team, service, or suite — with their own monitors, quarantining, and ticketing. | `--test-collection-id` | | Repository | Detected automatically from the git remote, and keeps test data separate between repositories and forks automatically. | Detected; `--repo-url` overrides | | Variant | Separate the *same* test run in different environments or architectures, so a flake on one doesn't condemn the other. | `--variant` | diff --git a/flaky-tests/management/github-pull-request-comments.mdx b/flaky-tests/management/github-pull-request-comments.mdx index 49290468..1e78531b 100644 --- a/flaky-tests/management/github-pull-request-comments.mdx +++ b/flaky-tests/management/github-pull-request-comments.mdx @@ -8,7 +8,7 @@ Flaky Tests can post comments on GitHub pull requests that summarize test result **Note:** Flaky Tests will only post a comment when there are failing tests. -Pull request comments are supported for repository-based flows only, not for [test collections](/flaky-tests/get-started/test-collections). For collection-scoped test results on a pull request, use the [browser extension](/merge-queue/browser-extensions). +Pull request comments are supported for repository-based flows only, not for [test collections](/flaky-tests/test-collections). For collection-scoped test results on a pull request, use the [browser extension](/merge-queue/browser-extensions). diff --git a/flaky-tests/management/managing-detected-flaky-tests.mdx b/flaky-tests/management/managing-detected-flaky-tests.mdx index bb5cc28a..85ef3a42 100644 --- a/flaky-tests/management/managing-detected-flaky-tests.mdx +++ b/flaky-tests/management/managing-detected-flaky-tests.mdx @@ -23,7 +23,7 @@ Go through these guides first to start detecting flaky tests. - Member access to the Trunk app to view and edit tests; Admin access if you also need to configure ticketing or webhook integrations -This workflow is the same whether your tests are organized by repository or by [test collection](/flaky-tests/get-started/test-collections) — labels, tickets, monitors, muting, flagging and quarantining all work per scope. A collection's **Tests** tab additionally filters by repository, since a collection can span several. +This workflow is the same whether your tests are organized by repository or by [test collection](/flaky-tests/test-collections) — labels, tickets, monitors, muting, flagging and quarantining all work per scope. A collection's **Tests** tab additionally filters by repository, since a collection can span several. ### Step 1: Organize tests with labels diff --git a/flaky-tests/management/ticketing/automatic-ticketing.mdx b/flaky-tests/management/ticketing/automatic-ticketing.mdx index 8e628152..d6aa9e3b 100644 --- a/flaky-tests/management/ticketing/automatic-ticketing.mdx +++ b/flaky-tests/management/ticketing/automatic-ticketing.mdx @@ -14,7 +14,7 @@ Automatic ticketing works with the built-in [Linear](./linear-integration), [Jir ## Enabling ticket automation -Connect an integration once for your organization, then choose it on each [test collection](/flaky-tests/get-started/test-collections) that should file tickets. +Connect an integration once for your organization, then choose it on each [test collection](/flaky-tests/test-collections) that should file tickets. 1. In the Trunk app, navigate to **Settings** → **Organization** → **Ticketing** and connect your Linear, Jira, or Asana integration. An organization can hold several — one Jira project for one team, another for a second. 2. Open the collection's **Settings** tab, then **Ticketing**, and select which of those integrations the collection files into by default. @@ -74,7 +74,7 @@ For Jira, the configured close/reopen target status must be reachable in a singl Repository-level ticketing works the same way, with the integration configured on the repository rather than the organization: navigate to **Settings** → **Repositories** → **[your repository]** → **Ticketing**. Every setting described above behaves identically. -The difference is flexibility: **a repository has exactly one ticketing integration and cannot file into any other.** Collections both choose from every integration connected to your organization and let you file a manual ticket into any of them, so [migrating to collections](/flaky-tests/migrate-to-test-collections) is what buys you more than one destination. +The difference is flexibility: **a repository has exactly one ticketing integration and cannot file into any other.** Collections both choose from every integration connected to your organization and let you file a manual ticket into any of them, so [migrating to collections](/flaky-tests/get-started/migrate-to-test-collections) is what buys you more than one destination. ## Legacy webhook-based ticket autocreation diff --git a/flaky-tests/overview.mdx b/flaky-tests/overview.mdx index d4b83417..5b953f78 100644 --- a/flaky-tests/overview.mdx +++ b/flaky-tests/overview.mdx @@ -5,7 +5,7 @@ og:title: "Trunk Flaky Tests overview" --- Trunk Flaky Tests lets your teams detect, track, quarantine, and fix **flaky tests** in your codebase. Trunk can also identify **broken tests** — tests failing consistently at a high rate that indicate real regressions needing immediate fixes, not just quarantining. Flaky Tests is language, environment, and framework-agnostic. -Tests are organized into [test collections](/flaky-tests/get-started/test-collections) — named groups, each with its own detection, quarantining and ticketing settings. New organizations start on collections; organizations already using Flaky Tests by repository [migrate to them gradually](/flaky-tests/migrate-to-test-collections). +Tests are organized into [test collections](/flaky-tests/test-collections) — named groups, each with its own detection, quarantining and ticketing settings. New organizations start on collections; organizations already using Flaky Tests by repository [migrate to them gradually](/flaky-tests/get-started/migrate-to-test-collections). Let's explore how Trunk Flaky Tests' features help you tackle flaky tests. If you can't wait to try Trunk, follow our [getting started guide](/flaky-tests/get-started). diff --git a/flaky-tests/quarantining/index.mdx b/flaky-tests/quarantining/index.mdx index a7db51ac..3156216e 100644 --- a/flaky-tests/quarantining/index.mdx +++ b/flaky-tests/quarantining/index.mdx @@ -66,7 +66,7 @@ Here's what each of these options does: ### Collection-level quarantining settings -[Test Collections](../get-started/test-collections) have their own quarantining settings, which lets you apply different quarantining policies to different subsets of your test suite. +[Test Collections](../test-collections) have their own quarantining settings, which lets you apply different quarantining policies to different subsets of your test suite. While you are migrating, which settings apply is decided per upload: **if quarantining is enabled on the collection an upload was routed to, that collection's quarantining and flaky state are used. Otherwise the repository's are.** diff --git a/flaky-tests/reference/api-reference.mdx b/flaky-tests/reference/api-reference.mdx index 36494e89..45313ad7 100644 --- a/flaky-tests/reference/api-reference.mdx +++ b/flaky-tests/reference/api-reference.mdx @@ -5,11 +5,11 @@ og:title: "Trunk Flaky Tests API reference" --- The Trunk Flaky Tests API is an HTTP REST API, returns JSON from all requests, and uses standard HTTP response codes. -**Endpoints come in two scopes, and they are not interchangeable.** Which one you want depends on how your tests are organized — see [migrating to test collections](/flaky-tests/migrate-to-test-collections) if you are moving between them. +**Endpoints come in two scopes, and they are not interchangeable.** Which one you want depends on how your tests are organized — see [migrating to test collections](/flaky-tests/get-started/migrate-to-test-collections) if you are moving between them. ## Test collection endpoints -Scoped to [test collections](/flaky-tests/get-started/test-collections), on `/v2`. Use these if your tests are organized into collections. +Scoped to [test collections](/flaky-tests/test-collections), on `/v2`. Use these if your tests are organized into collections. diff --git a/flaky-tests/reference/cli-reference.mdx b/flaky-tests/reference/cli-reference.mdx index e1ccbf1b..7551c599 100644 --- a/flaky-tests/reference/cli-reference.mdx +++ b/flaky-tests/reference/cli-reference.mdx @@ -148,7 +148,7 @@ Variant names are displayed in brackets next to test names in your dashboard: ## Test Collections -[Test collections](/flaky-tests/get-started/test-collections) group tests so they can be configured and reviewed together, with their own flake detection and quarantining. To upload into one, pass its ID with `--test-collection-id`: +[Test collections](/flaky-tests/test-collections) group tests so they can be configured and reviewed together, with their own flake detection and quarantining. To upload into one, pass its ID with `--test-collection-id`: ```sh Upload to a test collection ./trunk-analytics-cli upload --junit-paths "test_output.xml" \ @@ -278,7 +278,7 @@ The `upload` and `test` commands accept the following options: | `--use-bazel-target-for-codeowners` | When uploading a Bazel BEP file, use the Bazel target as a fallback path to associate test cases to codeowners. **Optional**. | | `--allow-empty-test-results` | Don't fail commands if test results are empty or missing. Use it when you sometimes skip all tests for certain CI jobs. Defaults to `true`. | | `--variant ` | Upload tests to a specific variant group. **Optional**. | -| `--test-collection-id ` | Upload to a [test collection](/flaky-tests/get-started/test-collections), in addition to (not instead of) `--org-url-slug`. Can also be set with the `TRUNK_TEST_COLLECTION_ID` environment variable. **Optional**. | +| `--test-collection-id ` | Upload to a [test collection](/flaky-tests/test-collections), in addition to (not instead of) `--org-url-slug`. Can also be set with the `TRUNK_TEST_COLLECTION_ID` environment variable. **Optional**. | | `--hide-test-collection-links` | Print repository links at the end of a run instead of test collection links. Only has an effect when a collection ID is passed. Can also be set with the `TRUNK_HIDE_TEST_COLLECTION_LINKS=true` environment variable. **Optional**. | | `--test-process-exit-code` `` | Specify the exit code of the test previously run. This is used by the upload command to identify errors that happen outside of the context of the test execution (such as build errors). | | `--dry-run` | Write the test results bundle to a local `./bundle_upload` directory instead of uploading it to Trunk. [Quarantining](../quarantining/#quarantining-without-uploading) still runs and still determines the exit code. Can also be set with the `TRUNK_DRY_RUN=true` environment variable. **Optional**. | diff --git a/flaky-tests/get-started/test-collections.mdx b/flaky-tests/test-collections.mdx similarity index 91% rename from flaky-tests/get-started/test-collections.mdx rename to flaky-tests/test-collections.mdx index f4a357a4..a4a2cb54 100644 --- a/flaky-tests/get-started/test-collections.mdx +++ b/flaky-tests/test-collections.mdx @@ -2,7 +2,6 @@ title: "Test Collections" description: "Group tests into named collections, each with its own flake detection, quarantining, and ticketing settings." og:title: "Organizing tests with collections in Trunk Flaky Tests" -hidden: true --- A test collection is a named group of tests with its own settings. Each collection has independent flake detection, quarantining, and ticketing, so you can hold fast unit tests and fragile end-to-end tests to different standards. @@ -60,9 +59,9 @@ Pass the collection ID to the uploader alongside your organization slug. Both ar --token $TRUNK_API_TOKEN ``` -You can set the ID as the `TRUNK_TEST_COLLECTION_ID` environment variable instead, or pass it as the `test-collection-id` input to the [uploader action](./ci-providers/github-actions). +You can set the ID as the `TRUNK_TEST_COLLECTION_ID` environment variable instead, or pass it as the `test-collection-id` input to the [uploader action](./get-started/ci-providers/github-actions). -Everything else about your setup is unchanged. Adding the collection ID to a working upload step is the whole change. See [**Test Frameworks**](./frameworks/) and [**CI Providers**](./ci-providers/) for the setup itself, and the [**CLI reference**](../reference/cli-reference#test-collections) for the full flag list. +Everything else about your setup is unchanged. Adding the collection ID to a working upload step is the whole change. See [**Test Frameworks**](./get-started/frameworks/) and [**CI Providers**](./get-started/ci-providers/) for the setup itself, and the [**CLI reference**](./reference/cli-reference#test-collections) for the full flag list. A CI job uploads to exactly one collection. To send results to more than one collection, add an upload step per collection. @@ -76,8 +75,8 @@ A CI job uploads to exactly one collection. To send results to more than one col | **Tests** | Every test in the collection, with health status, failure rates, and labels. | | **Uploads** | Upload history for the collection. | | **Quarantining** | Quarantine analytics for the collection. | -| **Monitors** | The collection's [flake detection monitors](../detection/). | -| **Settings** | The collection's name and description, [quarantining](../quarantining/), upload handling, and [ticketing](../management/ticketing/automatic-ticketing). | +| **Monitors** | The collection's [flake detection monitors](./detection/). | +| **Settings** | The collection's name and description, [quarantining](./quarantining/), upload handling, and [ticketing](./management/ticketing/automatic-ticketing). | ## Finish setting up a collection diff --git a/flaky-tests/webhooks/index.mdx b/flaky-tests/webhooks/index.mdx index cb93c49a..cdd8ae70 100644 --- a/flaky-tests/webhooks/index.mdx +++ b/flaky-tests/webhooks/index.mdx @@ -32,13 +32,13 @@ Trunk publishes three Flaky Tests event types to Svix. Each event includes a ful ## Test collection events -Events for [test collections](/flaky-tests/get-started/test-collections) carry the same event types, with one addition to the payload and one thing you cannot do with it. +Events for [test collections](/flaky-tests/test-collections) carry the same event types, with one addition to the payload and one thing you cannot do with it. **Telling the two apart.** A collection event carries a `test_collection` object — its ID and a link to the collection. Repository events don't. That object is the supported way to distinguish them. **You cannot deduplicate on `test_case.id`.** Collection and repository events do not share a test-case ID space, so the same underlying test arrives under two unrelated IDs. `repository.id` is the only handle common to both, and it is omitted rather than guessed when an upload carries no repository. -**While you are migrating, collection events are off.** A repository and a collection with monitors over the same tests detect independently, so one detection can produce two events. Switch collection events on from **Settings** → **Organization** → **Webhooks** once your consumer handles the payloads above. It is one switch for every collection event, not one per event type, and it disappears once you have finished migrating — at that point collection events are simply sent. See the [migration guide](/flaky-tests/migrate-to-test-collections#webhooks-while-you-migrate). +**While you are migrating, collection events are off.** A repository and a collection with monitors over the same tests detect independently, so one detection can produce two events. Switch collection events on from **Settings** → **Organization** → **Webhooks** once your consumer handles the payloads above. It is one switch for every collection event, not one per event type, and it disappears once you have finished migrating — at that point collection events are simply sent. See the [migration guide](/flaky-tests/get-started/migrate-to-test-collections#webhooks-while-you-migrate). ## Event payloads