anchor.diff:  * if you're making the request in a Buildkite pipeline, you can use the Buildkite [environment variables](/docs/pipelines/environment-variables#bk-env-vars) to set the metadata
   * if you're making it elsewhere, you'll need to set them yourself.
   
  -Test analytics uses the following environment variables in the `run_env` attribute to populate test information. The only required environment variable is `key`, but some features of Test Analytics aren't available if not all of the other environment variables in the following example are set:
  +Test analytics uses the following  variables in the `run_env` attribute to populate test information. The only required  variable is `key`, but some features of Test Analytics aren't available if not all of the other  variables in the following example are set:
   
   * `CI`
   * `key` (**required**)
  
positive.code: * if you're making the request in a Buildkite pipeline, you can use the Buildkite [environment variables](/docs/pipelines/environment-variables#bk-env-vars) to set the metadata
  * if you're making it elsewhere, you'll need to set them yourself.
  
  Test analytics uses the following environment variables in the `run_env` attribute to populate test information. The only required environment variable is `key`, but some features of Test Analytics aren't available if not all of the other environment variables in the following example are set:
  
  * `CI`
  * `key` (**required**)
  
negative.code:     $ git push
      ```
  
  5. Make sure that the Test Analytics [environment variables](#integrating-with-rspec-environment-variables) are set so that the RSpec integration can use them in your Test Analyitics dashboard.
  
  Once you’re done, in your Test analytics dashboard, you'll see analytics of test executions on all branches that include this code.
  
  ### Environment variables
  
  Test Analytics uses the following environment variables to populate test information. The only required environment variable is `BUILDKITE_ANALYTICS_KEY`, but some features of Test Analytics aren't available if not all of the other environment variables are set:
  
  * `BUILDKITE_ANALYTICS_KEY` - a unique key for the build that initiated the Test Analytics run
  * `BUILDKITE_ANALYTICS_URL` - a URL that links to the build
  * `BUILDKITE_ANALYTICS_BRANCH` - the branch or ref that this run is for
  * `BUILDKITE_ANALYTICS_SHA` - the commit sha for the head of the branch
  * `BUILDKITE_ANALYTICS_NUMBER` - the build number of the build
  * `BUILDKITE_ANALYTICS_JOB_ID` - the id of a job within the build
  * `BUILDKITE_ANALYTICS_MESSAGE` - the commit message for the head of the branch
  
  ### Supported continuous integration platforms
  
  Test Analytics works with
  
  * Buildkite
  * GitHub Actions
  * CircleCI
  
  <!-- Related PR: https://github.com/buildkite/rspec-buildkite-analytics/pull/80 -->
  
  Test Analytics can provide quick links from Test Analytics to your builds, regardless of your CI platform.
  
  <!-- TODO: check with team on how to describe what benefits this provides. I think there are more than just the link to build. -->
  
  ## Importing JUnit XML
  
  