James Talmage

Results 145 comments of James Talmage

> Now it will run all the tests before letting you know you have an issue and then you'll have to rerun the whole test file again. Just a thought....

Why not? If it increases the error count, that's noticeable immediately.

> Are there any concerns around cleanup code not running when tests are aborted? I would say yes. We could make it configurable. That would mean watch support now adds...

If you have all concurrent tests then this behavior is essentially useless. Tests will have begun by the time you send an abort. So if we follow up with afterEach...

I think I know what you are asking, and I am not objecting to the concept in general, I am just saying I don't see a practical way of accomplishing...

There is no such thing as a "next concurrent test". Every concurrent test in the file is launched in a single turn of the event loop, once you have kicked...

I'm +1 for zeit/now. We'll get documentation builds integrated into every commit / PR / etc for free. Implementing a drop down that lets you choose which release you're looking...

See: https://github.com/avajs/eslint-plugin-ava/blob/master/docs/rules/no-skip-test.md

`tap`/`tape` shows you every assertion failure. Usually, yes - you only need to see the first assertion. Though sometimes additional information can be helpful: ``` js var a = sum(2,...