James Talmage

If / when this is implemented, please submit an issue or PR to [`supports-hyperlinks`](https://github.com/jamestalmage/supports-hyperlinks), which is intended to detect support for this capability.

@Tyriar - In that case, perhaps just include a reference to `supports-hyperlinks` in the commit that lands this, and in the release notes when it goes wide. I'm not sure...

No, idea if this is even still an issue, but I'm closing related PR https://github.com/browserify/browserify/pull/1583 It provided a reproduction.

I think separate keyboard shortcut, but the "run all" should be the "default one" (i.e. require less modifier keys be pressed). I don't recall what the exact keyboard shortcut was...

With multiple files, the test title should reflect the file it's run in: ``` $ ./cli.js --tap test/fixture/es2015.js test/fixture/async-await.js TAP version 13 # es2015 › [anonymous] ok 1 - es2015...

If you are using the AVA CLI, then you don't need to do anything. If there is a single file, the file name is prepended, otherwise it is not. -...

> given a list of files in an Atom project, I should be able to get only the JS files that could contain tests Just running `ava` in the main...

Start building your integration / UI with the "friendly" one. We will add an option or extra yaml property to get you the full file eventually

But presumably you should know how your code is calling the mock (with new, or without), and if we are mocking a `class`, then we aren't testing that `class`, but...

At a minimum there should be an easier way to verify it was called with `new`, perhaps just: ```js td.verify(new foo(arg 1, arg 2)); ``` But in that's the API...