Unflakable — Protect your builds from flaky tests

Description

“ Hello Product Hunters! As a software engineer who has worked at multiple fast-growing startups, I've experienced first-hand how frustrating flaky tests can be. Just when you’re ready to merge a cool new feature, a test unrelated to your change fails, causing the entire continuous integration (CI) build to fail. This happens all too often, forcing developers to retry the entire CI pipeline (sometimes more than once!), which can delay code merges by hours. Over time, these spurious test failures lead developers down a dark path to work around the issue by reflexively retrying CI failures or even preemptively running multiple CI attempts in parallel. The end result is plummeting productivity, skyrocketing CI costs, and frustrated developers considering other employment opportunities. I decided to build Unflakable because automated testing and CI should exist to help developers build high-quality products—not to hold them back. Unflakable is a service that plugs into existing CI workflows with minimal setup and allows developers to track and quarantine flaky tests. It automatically retries individual test failures during CI runs to distinguish flaky tests from true test failures and sends notifications whenever new flaky tests are discovered. Unflakable can automatically quarantine flaky tests so that future failures won’t lead to failed CI runs until teams have had an opportunity to fix the tests. With Unflakable, developers can be confident that when a CI run fails, it’s for a legitimate reason that’s worth their time to investigate. Unflakable is now in beta, with support for JavaScript/TypeScript tests using the Jest testing framework. Python support is just around the corner, and support for other languages and test frameworks is coming soon. Unflakable’s current features are FREE, and a paid tier with plenty of additional features is expected to launch later this year. If your team is suffering from flaky tests, I would love to have you join the beta and provide early feedback! ” – David Ramos Discussion | Link