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
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
We've seen all kinds of flaky tests across hundreds of customers: Here's a tactical guide on our learnings so far on how to fix flaky tests, as well as establish best practices in your org so they don't cause pain in the future!
1
2
5
953
We can help out here with test quarantining and root cause analysis - BuildPulse aims to speed up your CI system
14
We can help with flaky tests!
20
We can help out here! BuildPulse is a platform for detecting, reporting impact, quarantining, and ultimately fixing flaky tests
21
Replying to @yagiznizipli
We can help here! We help you detect, report impact, quarantine, and ultimately fix flaky tests
1
115
Check out buildpulse.io to deflake today
1
123
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?
1
1
165
Stability: - Disruptive tests introduce unexpected product behaviors - Unreliable testing increases the likelihood of downtime - Flaky tests give teams a false sense of coverage confidence
1
2
13
Velocity: - Re-running your tests consume developer time and increase infrastructure costs - Broken builds delay your releases - Burdensome merges between long builds
1
1
14
3 reasons why your flaky test problem needs to be solved ASAP
2
1
1
289
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!
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
1
3
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!
1
4
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
2
4
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 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….
Replying to @BuildPulseApp
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 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….
Replying to @BuildPulseApp
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…
1
That URL ☝️ currently points to the v0.19.0 release at github.com/buildpulse/test-r…. This is the latest production release (published in July). The binary itself is unchanged. Only the filename has changed to work around the download issue.
1