Company
Word count
354
Language
English
Contains code?

Text

Aviator fetches the test results by using a custom plugin. Currently, we support CircleCI and Buildkite integrations. For both plugins, you need to specify two things:

AVIATOR_API_TOKEN

to associate the data with your account and the files associated with the test artifacts. CircleCI Step 1 : Configure the API token in the environment variables section as: Copy

AVIATOR_API_TOKEN=av_live_xxxxxxx

Step 2 : Add a step after your test execution step. Copy

version: 2.1
orbs:
  aviator-upload-orb: aviator/[email protected]
jobs:
  test:
    docker:
      - image: cimg/python:3.7
    steps:
      - checkout
      - run:
          name: Run tests and upload results
          command: |
            python -m pytest -vv --junitxml="test_results/output.xml"
      - aviator-upload-orb/upload:
          assets: "test_results/*.xml"
workflows:
  test-and-upload:
    jobs:
      - test

Once this is done, you should be able to verify that the artifacts are getting uploaded by looking at your CircleCI. You should see something like: The

aviator-upload-orb

used above is available publicly at aviator-co/circleci-upload-orb . Buildkite To install Aviator on Buildkite, please use the Buildkite plugin defined here . Step 1 : Configure the API token as a secret in Buildkite. You can set this in an environment hook on Buildkite agents or use your preferred secret storage. Read more about managing Buildkite secrets . Step 2 : Now you can either upload the artifacts from the same step as the test run or create a separate step: Option A: From build step To upload all files from an XML folder from a build step: Option B: Using build artifacts You can also use build artifacts generated in a previous step: GitHub Actions Step 1 : Configure the API token as a secret in your repository . Step 2 : Add the GitHub Action as a step in your job. Make sure to specify the inputs

assets

and

aviator_api_token

. Add the conditional

if: success() || failure()

in the step to ensure that the test files are always uploaded, regardless of test failure/success. The GitHub action is available publicly at aviator-co/upload-action . You can also find it on the GitHub Marketplace . Last updated 1 year ago Was this helpful?

Analysis

No analysis created yet for this page.