Alternatives
Products that do what Retestees does
Find flaky tests and wasted CI time in GitHub Actions
- 1
- 2
Detect CI waste and flaky workflows in GitHub Actions
Mar 2026 · ci-governor-c3ke.onrender.com
- 3
- 4
- 5GB
2020 · github.com
- 6
- 7
- 8
- 9
- 10
- 11
- 12AC
2023 · github.com
- 13IB
I got sick of the old software development loop: Change code -> Run tests -> wait -> wait some more -> look at failures. I decided to build a tool that will enable you to: Change code -> look at failures. No wait time, no explicit test running. Under the hood: - Runs the whole test suite and collects code coverage per test. - For each auto file save, analyzes the changes on the tests. - Runs changed tests in the background. - Display results, the loop time from change to test results is approx 250ms. Instead of: code -> alt+tab -> arrow up -> rerun all the tests -> wait ... -> test results…
2022 · github.com
- 14
- 15
- 16
- 17
- 18
- 19TY
2021 · github.com
- 20WG
For the past month, we've been monitoring GitHub's public event stream to catch spam comments and fake stars. Today, the spammers are back. Go check out the damage! You can see the spam comments and which users are posting the spam in real time. Also, here's a post we wrote about how we set it up: https://www.trytrench.com/blog/preventing-spam-and-fake-star...
2024 · play.trytrench.com
- 21CA
Hi HN! We’re Clemens and Felix from Cito - thrilled to show you what we’ve built to help data engineers stay on top of data quality issues. Think Datadog meets Incident.io. Tests in dbt are great when checking whether specific expectations are true, but don’t work well for use cases where data patterns may change over time. When relying on testing alone, data teams regularly face situations where business stakeholders identify data issues in dashboards first, eroding trust. In such situations, understanding the implications of an issue and debugging can be a very manual and time-consuming…
2022 · citodata.com
- 22IB
I built a GitHub app that detects it in pull requests, notifies or blocks them. Alongside it, I published a Semgrep ruleset for any stage of the CI/CD. I started this after getting frustrated by all the FUD around malicious code - lots of noise, little effort to solve it. Having said that, it's still a major attack vector - a stored RCE, with the codebase itself as the sink. Feedback is appreciated. The app, PRevent - https://github.com/apiiro/PRevent The ruleset: https://github.com/apiiro/malicious-code-ruleset The research:…
2025 · github.com
- 23AF
Hi HN, my team and I have been working on a new tool to improve how bugs are reported to engineers. I used to be a developer, and I thought it was ridiculous the little amount of bug repro details I would get in JIRA tickets. Then I became a product manager, and I realized how time consuming and tedious it was to write good tickets for developers (and then understood why most tickets lack enough detail!) That’s why my team and I decided to build a browser extension for anyone to create bug reports that auto-include: console logs, network requests, session replay, timestamp, url, browser, OS…
2022 · jam.dev
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →