Viewing profile — _cfl0

I built haystack - natural language search engine for workplace technical knowledge. I've been a software engineer for a few years now, A few weeks ago I was scrolling through conf…

Sure, read docs.nabaz.io (CI solution w/ storage over mongodb)

You aren't interrupted, you choose when to alt+tab to see your test results.

Main difference is that crystalball still runs all the tests, but runs the recently failed ones first. Nabaz selects a small subset of affected tests, reducing CPU usage, and more …

10.

Nx is even clealry different. It isn’t run on every code change, but on commits. You can’t use it live, And also the analysis granularity is just way too wide compared to this.

Right.. Because out of a 100 tests it will run close to that number. when you change code most of the time only a handful of tests or less need to run.

Had what since forever? Does jest analyze the changes you make and compare them to code coverage? (hint: no) The key innovation piece here is the speed that the extreme selectively…

I also have a CI solution I’m launching soon. Other than that, most of this tech was forgotten in the late 90s early 2000s

Not bulletproof, but a-ok if your running a full run just before the commit.

Toda ;)

The second part is the aim here. This is more of a code watcher than a test watcher specifically.

collab w/ me ;)

Not only the time to boot, but also if you don’t run tests selectively, you’re already too slow.

Furthermore, it will still display the build error + the previous failure list. So you can always rely on that background terminal for actual test failure reasons.

Problem being is “make && make check” take way too much time normally.

The ordering feature is actually being built as we speak. analyzing liklihood can still be beneficial to cut down time even more. If I would get a break from hn comments I could fi…

1. No, if build fails hypertest will just discard the result. autosave is even prefered. 2. The first run and every subsequent one collects code coverage which is saved in an sqlit…

Love that mantra! Dont really agree, it’s not intended for that. I use it as I would run tests through a terminal normally. Built this because I hate running tests.

Bazel is awesome, it just runs way too many tests to be fast enough

Well, I would say the biggest difference is while the watch mode you described runs all the tests for every change. hypertest only runs the tests the were impacted by the changed c…

Appreciated! Would love to hear you’re feedback after you ran it also :)