HackerTrans
TopNewTrendsCommentsPastAskShowJobs

_cfl0

no profile record

Submissions

[untitled]

1 points·by _cfl0·há 4 anos·0 comments

Show HN: I built a tool to get instant test results

github.com
96 points·by _cfl0·há 4 anos·63 comments

Show HN: Hypertest - A test runner for developers with ADHD

nabaz.io
14 points·by _cfl0·há 4 anos·3 comments

Show HN: We built a tool for fast-forwarding 95% of tests (MIT)

github.com
8 points·by _cfl0·há 4 anos·17 comments

comments

_cfl0
·há 4 anos·discuss
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 our jenkins second integration machine for 40 minutes straight, later I discovered my co-worker slack'ed me the ssh connection string *two months ago*.

A week later I started working on haystack - a search engine for workplace apps.. It enables you to search slack, confluence, jira, teams, sharepoint, github, and email in one place.

It supports natural language queries so a query like: "how to connect to integ2 machine?" yields:

  ssh -i private.pem [email protected]
Privacy?

haystack is self hosted and stores user data locally, it has a completely client-side version, and a a self-hosted docker container version - only you have access to internal docs, I didn't want to deal with security compliance headaches caused from storing user data in the cloud + I don’t want your internal docs/messages.

Rolled it out to my co-workers a week ago and they thought it's a hit, so I'm planning on releasing it publicly on March 2023.

*Early access*

More technical details are available on github, code released on March 23’:

<https://github.com/haystackoss/haystack>

If you want to try it out before March 2023 - Available here <https://haystack.it>
_cfl0
·há 4 anos·discuss
Sure, read docs.nabaz.io (CI solution w/ storage over mongodb)
_cfl0
·há 4 anos·discuss
You aren't interrupted, you choose when to alt+tab to see your test results.
_cfl0
·há 4 anos·discuss
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!
_cfl0
·há 4 anos·discuss
10.
_cfl0
·há 4 anos·discuss
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.
_cfl0
·há 4 anos·discuss
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.
_cfl0
·há 4 anos·discuss
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.
_cfl0
·há 4 anos·discuss
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
_cfl0
·há 4 anos·discuss
Not bulletproof, but a-ok if your running a full run just before the commit.
_cfl0
·há 4 anos·discuss
Toda ;)
_cfl0
·há 4 anos·discuss
The second part is the aim here.

This is more of a code watcher than a test watcher specifically.
_cfl0
·há 4 anos·discuss
collab w/ me ;)
_cfl0
·há 4 anos·discuss
Not only the time to boot, but also if you don’t run tests selectively, you’re already too slow.
_cfl0
·há 4 anos·discuss
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.
_cfl0
·há 4 anos·discuss
Problem being is “make && make check” take way too much time normally.
_cfl0
·há 4 anos·discuss
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 ;)
_cfl0
·há 4 anos·discuss
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.

Although this approach isnt perfect, The idea here is being fast. I always rerun the entire suite just before committing the code.
_cfl0
·há 4 anos·discuss
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.
_cfl0
·há 4 anos·discuss
Bazel is awesome, it just runs way too many tests to be fast enough