I built a tool to get instant test results
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…
In plain words
This tool automates test execution for software developers by running only the affected tests whenever code is saved, eliminating wait times in the development cycle. It analyzes code changes against test coverage data and displays results in approximately 250 milliseconds, allowing developers to see test failures immediately after making changes. The tool is designed for developers who want to streamline their workflow and reduce context switching during coding sessions.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
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 code -> alt+tab -> test results! Check it out! <https://github.com/nabaz-io/nabaz>
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 2d ago · opentrailpaper.com
Launched alongside, November 2022
the whole month →
- TC
I made a thing! In 2014, I was holding a stack of iPhones and thought to myself: "Hey, if I had each phone display a playing card, I could click a button and they'd shuffle themselves" I pared that idea all the way down to this: trading cards made of e-ink displays. Right now, each card costs me about $20 each, but with only a bit more scale, I think I can get that down to $10. In doing this project, I learned how to design electronics and circuit boards. I learned Rust and wrote my first driver, I upped my CAD skills, 3D printed, and did my first resin casting. I generated the images on the…
Dev tools · 2022 · wyldcard.io
