anchor.diff:      )
       ```
   
  -1. [Securely](/docs/pipelines/secrets) set the `BUILDKITE_ANALYTICS_TOKEN` secret on your CI to the API token from earlier. If you're testing an Xcode project, remember that Xcode doesn't automatically pass environment variables to the test runner, so you need to add them manually. In your test scheme or test plan, go to the _environment variables_ section and add the following key-value pair:
  -
  -    * key: `BUILDKITE_ANALYTICS_TOKEN`
  -    * value: `$(BUILDKITE_ANALYTICS_TOKEN)`
  -
  -1. Push your changes to a branch, and open a pull request. After a test run has been triggered, results will start appearing in your analytics dashboard
  +1. Commit and push your changes:
   
       ```bash
       git checkout -b add-buildkite-test-analytics
  
positive.code: 
  Before you start, make sure XCTest runs with access to [CI environment variables](/docs/test-analytics/ci-environments).
  
  1. [Create a test suite](https://buildkite.com/docs/test-analytics), and copy the _Buildkite Test Analytics API token_ you see
  
  1. Add the `test-collector-swift` repository to the `Package.swift` manifest, and add `BuildkiteTestCollector` to any test target requiring analytics:
  
      ```swift
      let package = Package(
  
negative.code:     git push origin add-buildkite-test-analytics
      ```
  
  Once you're done, in your Test Analytics dashboard, you'll see analytics of test executions on all branches that include this code.
  
  If you don't see branch names, build numbers, or commit hashes in Test Analytics, then read [CI Environments](/docs/test-analytics/ci-environments) to learn more about exporting your environment to the collector.
  
  ### Debugging
  
  To enable debugging output, set the `BUILDKITE_ANALYTICS_DEBUG_ENABLED` environment variable to `true`.
  