Easily connect your CircleCI jobs to BuildPulse to help you find and fix flaky tests.
See this orb's listing in CircleCI's Orbs Registry for details on usage, or see the example below.
In this example config.yml snippet, after your tests run, the buildpulse/upload command sends the test results to BuildPulse for analysis.
version: 2.1
orbs:
buildpulse: workshop64/buildpulse@x.y
jobs:
build:
docker:
- image: circleci/<some-docker-image>
steps:
- checkout
- run: echo "Run your tests and generate XML reports for your test results"
- buildpulse/upload:
account-id: 123
repository-id: 123
path: ./spec/reports
access-key-id: BUILDPULSE_ACCESS_KEY_ID
secret-access-key: BUILDPULSE_SECRET_ACCESS_KEY
path: test/reports # path to JUnit XML file
account-id: <buildpulse-account-id>
repository-id: <buildpulse-repository-id>
coverage-files: ./coverage/lcov/project.lcov # optional
tags: tag1 tag2 tag3 # optional
workflows:
version: 2
commit:
jobs:
- build