_cfl0

5 ms·

1.
by _cfl0 4y ago
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 confluence pages trying to find ssh connection details to o
2.
by _cfl0 4y ago
Sure, read docs.nabaz.io (CI solution w/ storage over mongodb)
3.
by _cfl0 4y ago
You aren't interrupted, you choose when to alt+tab to see your test results.
4.
by _cfl0 4y ago
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 importantly improving speed drastically!
5.
by _cfl0 4y ago
10.
6.
by _cfl0 4y ago
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.
7.
by _cfl0 4y ago
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.
8.
by _cfl0 4y ago
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 enables you.
9.
by _cfl0 4y ago
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
10.
by _cfl0 4y ago
Not bulletproof, but a-ok if your running a full run just before the commit.
11.
by _cfl0 4y ago
Toda ;)
12.
by _cfl0 4y ago
The second part is the aim here. This is more of a code watcher than a test watcher specifically.
13.
by _cfl0 4y ago
collab w/ me ;)
14.
by _cfl0 4y ago
Not only the time to boot, but also if you don’t run tests selectively, you’re already too slow.
15.
by _cfl0 4y ago
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.
16.
by _cfl0 4y ago
Problem being is “make && make check” take way too much time normally.
17.
by _cfl0 4y ago
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 finish it today lol ;)
18.
by _cfl0 4y ago
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 sqlite db. Every file change is compared to the code coverage. Al
19.
by _cfl0 4y ago
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.
20.
by _cfl0 4y ago
Bazel is awesome, it just runs way too many tests to be fast enough
21.
by _cfl0 4y ago
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 code. Resulting is blazing fast performance. I’d say it’s eve
22.
by _cfl0 4y ago
Appreciated! Would love to hear you’re feedback after you ran it also :)
23.
Show HN: I built a tool to get instant test results(github.com)
96 points by _cfl0 4y ago|63 comments
24.
by _cfl0 4y ago
Well, I wouldn't say i'm being selfless here, I benefit as a user lol :)
25.
by _cfl0 4y ago
Some background, I was diagnosed with ADHD when I was 5, moved in and out of schools through elementry/middleschool, ultimatly dropped out of highschool, I'm familiar with ADHD ;) If you have any suggestions/feature-requests.
26.
Show HN: Hypertest - A test runner for developers with ADHD(nabaz.io)
14 points by _cfl0 4y ago|3 comments
27.
by _cfl0 4y ago
We love gta! A few key differences though: 1. We analyze the effect of code changed on code coverage, which means we only compare changed code to runtime information (code that actually ran). gta analyzes statically. Let's assume
28.
by _cfl0 4y ago
Thanks guys for all your feedback! We took all notes to heart, the main problem we identified that currently (at this stage of the product cycle we don't yet support all edge cases) And this hurts usability and value, will figure out a
29.
by _cfl0 4y ago
THIS point though, Im inclined to share our edge case doc with HN and let people add stuff.
30.
by _cfl0 4y ago
Basically all of them as long as their used. Would love to know more about your use case, email is somewhere in the comments

More ›