Report Jest test results in Buildkite output as Annotations.
Install the package:
npm install -D jest-buildkite-reporter
# or
yarn add -D jest-buildkite-reporterAdd it your Jest reporters configuration. If you don't have any reporters you should also add the default one or you will lose the console output.
module.exports = {
reporters: ["default", "jest-buildkite-reporter"],
};The reporter only run when it detect that buildkite is present, so there is no need to conditionally include it.
When your tests are running in a docker containter they won't have access to buildkite by default and some environment variables need to be passed to them.
When jest is called as a RUN step inside the Dockerfile it need to specify the following args:
ARG BUILDKITE
ARG BUILDKITE_AGENT_ACCESS_TOKEN
ARG BUILDKITE_JOB_ID
RUN yarn jestAnd they need to be passed to the docker build command:
docker build --build-arg BUILDKITE --build-arg BUILDKITE_AGENT_ACCESS_TOKEN --build-arg BUILDKITE_JOB_ID .This projects uses Semantic Release. To publish a new version, ensure you have pushed to the main branch,
and use one of the following commit message types to trigger a release:
| Commit message | Release type |
|---|---|
fix(pencil): stop graphite breaking when too much pressure applied |
|
feat(pencil): add 'graphiteWidth' option |
|
perf(pencil): remove graphiteWidth optionBREAKING CHANGE: The graphiteWidth option has been removed.The default graphite width of 10mm is always used for performance reasons. |
(Note that the BREAKING CHANGE: token must be in the footer of the commit) |
This project is using the MIT license.
- junit-annotate-buildkite-plugin Official Buildkite plugin for JUnit
- jest-teamcity-reporter Jest reporter for TeamCity
- jest-teamcity Another Jest reporter for TeamCity
- bugcrowd-test-summary-buildkite-plugin BugCrowd reporter for BuildKite