BuildPulse Example Project: Java + Gradle + JUnit

This is an example JUnit project demonstrating how to send test results to BuildPulse to help you detect, track, and eliminate flaky tests.

Connect JUnit to BuildPulse

After starting a free trial, you can add BuildPulse to your project in just a few quick steps:

1. Identify the directory where your build is writing JUnit's XML test reports. (If you're using Gradle, the reports are written to <project-root>/build/test-results by default.)

2. Then, configure your build to send the JUnit XML reports to BuildPulse. [example]

   The configuration relies on your BuildPulse account ID, repository ID, key, and secret. You'll see this information when viewing your repository on buildpulse.io.

   This example uses GitHub Actions CI, but you can integrate just as easily with other CI providers as described below.

Works with the CI you already have

BuildPulse offers integrations for:

• CircleCI [docs]
• GitHub Actions [docs]
• Semaphore [docs]
• Travis CI [docs]
• Buildkite (available in early access)
• Jenkins (available in early access)
• webapp.io (available in early access)

Don't see your CI provider? Get in touch and we may be able to quickly add support for it.

---

Automatically detect flaky tests. Focus on the top offenders to quickly improve your builds. Save developer time and frustration. Regain trust in your test suite.

👉 Get started at buildpulse.io