:stop-on-first-failure (Autotest Option)

[klauswuestefeld]

I find myself scrolling up the repl to the first failure after a test run all the time.

Is it just me?

[arichiardi]

👍

[marick]

I'm wondering if it might be useful to have a way to tell autotest to "narrow in on this namespace". That is, keep tracking dependencies in all the sources, but only do reloading if a change would affect the namespace you're focused on.

When I get annoyed by this, I sometimes tell autotest to only consider two files - the source I'm working on and the file with its tests. But that involves enough typing that I don't do it regularly.

Question: when you're doing the scrolling, are you typically scrolling past N following failures?

[klauswuestefeld]

Yes.
On Jul 20, 2015 10:49 AM, "Brian Marick" notifications@github.com wrote:

I'm wondering if it might be useful to have a way to tell autotest to
"narrow in on this namespace". That is, keep tracking dependencies in all
the sources, but only do reloading if a change would affect the namespace
you're focused on.

When I get annoyed by this, I sometimes tell autotest to only consider two
files - the source I'm working on and the file with its tests. But that
involves enough typing that I don't do it regularly.

Question: when you're doing the scrolling, are you typically scrolling
past N following failures?

—
Reply to this email directly or view it on GitHub
#318 (comment).