Reduce cost and unlock developer time. BuildPulse runs your GitHub Actions jobs 2x faster, half cost and also fixes flaky tests.
New York, New York
Joined February 2019
- Tweets44
- Following10
- Followers68
- Likes551
Culture:
- Flaky tests erode trust in your testing environment
- Companies without a solid testing culture face more outages from untested code
- Why should developers trust tests if they are unreliable?
v0.23 of the BuildPulse test-reporter adds beta support for running on Windows! 🪟
github.com/buildpulse/test-r…
This joins the existing support for Linux and macOS. 🐧🍏
Now, no matter what OS(es) your CI runs on, flaky tests have nowhere to hide!
BuildPulse retweeted
Growing @BuildPulseApp's collection of example repos for identifying flaky tests in popular testing frameworks.
For JDK devs ☕, the collection now includes JUnit, ScalaTest, and TestNG: github.com/buildpulse?q=buil…
/cc @junitteam @ScalaTest
ALT List of example repositories for detecting flaky tests in various testing frameworks with @BuildPulseApp
BuildPulse retweeted
This was a nice surprise. A community-authored Discord integration for @BuildPulseApp:
github.com/Rabatta-ApS/Build…
Cool to see customers building their own automations on top of the BuildPulse API, and then making those automations available to others!
BuildPulse retweeted
Been expanding @BuildPulseApp's library of example repos for detecting flaky tests in various testing frameworks. 📈
Now includes Jest for JavaScript, pytest for Python, PHPUnit for PHP, and more. github.com/buildpulse?q=buil…
/cc @fbjest @pytestdotorg @phpunit
ALT List of example repositories for detecting flaky tests in various testing frameworks with @BuildPulseApp
We've reached out to affected customers regarding the resolution for this issue.
If you're still seeing this issue and you haven't heard from us or you'd like a hand, please get in touch so we can help: [email protected]
We're seeing reports of errors downloading the BuildPulse test-reporter binary. The download fails with a "403 forbidden" error when fetching the binary from GitHub releases.
We're actively investigating the issue and will follow up soon.
If you're using the BuildPulse GitHub Action to upload test results to BuildPulse, we've published v0.6.0 which resolves the `403 forbidden` errors: github.com/Workshop64/buildp…
This release updates the test-reporter URL to match the recommendation noted in xitter.cf/BuildPulseApp/status/1….
We think we've isolated the issue to a change in filename handling in @GitHub Releases.
If your CI script includes the URL for the BuildPulse test-reporter binary, you can resolve the issue by updating your script to use the following URL:
github.com/buildpulse/test-r…
If you're using the BuildPulse CircleCI Orb to upload test results to BuildPulse, we've published v0.7.0 which resolves the `403 forbidden` errors: circleci.com/developer/orbs/…
This release updates the test-reporter URL to match the recommendation noted in xitter.cf/BuildPulseApp/status/1….
We think we've isolated the issue to a change in filename handling in @GitHub Releases.
If your CI script includes the URL for the BuildPulse test-reporter binary, you can resolve the issue by updating your script to use the following URL:
github.com/buildpulse/test-r…
BuildPulse retweeted
Homebrew found @BuildPulseApp really useful. It finds and tracks our flaky tests so we can fix (or delete) them to improve the reliability of our test suite. It even notifies us in Slack:
BuildPulse retweeted
Wondering if that CI failure is a known flaky test?
Now you can search in @BuildPulseApp to find out. 🔍
BuildPulse retweeted
Cool to see the @BuildPulseApp test-reporter available in @MacHomebrew 🍺
Shout-out to @carlocab_ for whipping up the formula and getting it shipped! ⚡️
ALT Terminal window showing buildpulse-test-reporter in Homebrew search results for tools related to flaky tests