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

#1

Post by _cfl0 » Wed, Nov 16, 2022, 2:39 PM UTC

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>

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

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

#2

Post by [deleted] » Wed, Nov 16, 2022, 2:39 PM UTC

[deleted]

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

#3

Post by [deleted] » Wed, Nov 16, 2022, 2:49 PM UTC

[deleted]

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

#4

Post by [deleted] » Wed, Nov 16, 2022, 2:51 PM UTC

[deleted] wrote: post #3

[deleted]

[deleted]

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

#5

Post by newbieuser » Wed, Nov 16, 2022, 2:54 PM UTC

most test runners probably only support running tests that change. it's a good idea to collect this in one tool. good job

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

#6

Post by jwhiles » Wed, Nov 16, 2022, 2:59 PM UTC

I'm a bit confused how this differs from the existing watch modes that are built into test runners I'm familiar with, such as Jest. Is this something that I'm used to in TypeScript, but which just doesn't exist in most language's ecosystems?

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

#7

Post by _cfl0 » Wed, Nov 16, 2022, 3:01 PM UTC

newbieuser wrote: post #5

most test runners probably only support running tests that change. it's a good idea to collect this in one tool. good job

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

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

#8

Post by sgeisenh » Wed, Nov 16, 2022, 3:01 PM UTC

For folks using bazel, there is also [bazel-watcher][1]. Also worth checking out [watchman][2] for this style of workflow in general.

[1]: https://github.com/bazelbuild/bazel-watcher [2]: https://facebook.github.io/watchman/

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

#9

Post by _cfl0 » Wed, Nov 16, 2022, 3:04 PM UTC

jwhiles wrote: post #6

I'm a bit confused how this differs from the existing watch modes that are built into test runners I'm familiar with, such as Jest. Is this something that I'm used to in TypeScript, but which just doesn't exist in most language's ecosystems?

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 even fast than apples alt+tab animation most of the time.

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

#10

Post by daveguy » Wed, Nov 16, 2022, 3:04 PM UTC

I like the concept and it seems that "run them all and see what changed" is a great model to avoid missing any side effects from a code change. However, if you're running all the tests on every change, doesn't that mean the responsiveness is necessarily greater than 250ms if your test suite is longer than 250ms?

Regardless, running tests in the background to eliminate human delay is good. It would be nice if the (~test time)*(test change likelihood) of the tests were used to order tests based on fastest relevant feedback.

A code->test change likelihood map may also be used to reveal previously unexpected dependencies. Also ~test time could be difficult (see halting problem and windows time remaining estimates).

This is good work.