Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

61–68 of 68 posts

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

#61

Post by _cfl0 »

Cthulhu_ wrote: post #42
_cfl0 wrote: post #9

Earlier quoted context omitted.

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.

> Well, I would say the biggest difference is while the watch mode you described runs all the tests for every change. This is not true though. Might depend on the test tooling used, but most of the ones I've used only run changed tests (either directly or through change detection via git, e.g. https://nx.dev/concepts/affected )

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.

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

#62

Post by _cfl0 »

lupire wrote: post #46
Cthulhu_ wrote: post #42

Earlier quoted context omitted.

> Well, I would say the biggest difference is while the watch mode you described runs all the tests for every change. This is not true though. Might depend on the test tooling used, but most of the ones I've used only run changed tests (either directly or through change detection via git, e.g. https://nx.dev/concepts/affected )

Let's say you have 100 tests that depend on the file being changed, but only 10 that depend on the method or line changed since last year run. How many tests will your system run? That's the important question.

10.

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

#63

Post by yardstick »

bagels wrote: post #54
yardstick wrote: post #51

> hypertest is an open-source CLI tool designed to help you maintain focus on the current coding subtask, built specifically for the easily distracted. I don’t quite get this proposition. If easily distracted, and wanting to stay focused, wouldn’t you rather want to run tests only on demand and not be interrupted by failing tests after changing just a line or two and still not finished with the rest of your changes.…

If you are already running tests after every save, and watching for the outcome, but the test takes too long, you might get distracted waiting for the test

Sure. I would suggest a different workflow rather than trying to optimise the current workflow.

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

#65

Post by _cfl0 »

grncdr wrote: post #53
twic wrote: post #38

This sounds a lot like a couple of old JUnit test runners: InfiniTest - https://infinitest.github.io/ an d https://infinitest.github.io/doc/intellij#how-it-works JUnit Max - https://web.archive.org/web/20090206151635/http://www.threer... partially surviving as https://junit.org/junit4/javadoc/4.12/org/junit/experimental... Ruby has something similar: autotest - https://github.com/grosser/autotest I think it's a good…

Ruby also has crystalball ( https://toptal.github.io/crystalball/ ) which is similar, but not quite the same.

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!

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

#66

Post by berkay »

theptip wrote: post #50

“Test impact analysis” is one name for this general approach. There are a few projects doing this in the Python ecosystem that don’t fully work (Smother, pytest-tia, and some others). Great to see another entry. Can you cache the coverage DB so this can be run in a CI pipeline?

Foresight does this if you're using github actions for CI. https://www.runforesight.com/test-gap-analysis (disclaimer: one of the founders)

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

#67

Post by _cfl0 »

yardstick wrote: post #51

> hypertest is an open-source CLI tool designed to help you maintain focus on the current coding subtask, built specifically for the easily distracted. I don’t quite get this proposition. If easily distracted, and wanting to stay focused, wouldn’t you rather want to run tests only on demand and not be interrupted by failing tests after changing just a line or two and still not finished with the rest of your changes.…

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

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

#68

Post by _cfl0 »

theptip wrote: post #50

“Test impact analysis” is one name for this general approach. There are a few projects doing this in the Python ecosystem that don’t fully work (Smother, pytest-tia, and some others). Great to see another entry. Can you cache the coverage DB so this can be run in a CI pipeline?

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