It would be nice to fix code style from selected code:

With #8, you have to go into the test file you want to run. Would be nice if you could run all tests in a project from anywhere in the project, even if no files are open. Since we're just spawning AVA, we can just spawn it without any file arguments and it will handle the logic of finding the project root and running all test files.

Should we have a separate keyboard shortcut for this? Or maybe we could always run all files unless the user is in a specific test file, then we just run that test file? Or is that too magic?

// @jacobmendoza

Recently, when I try to run ava test inside atom, it gives following error:

Uncaught TypeError: Cannot read property 'getPaths' of undefined
/Users/sunkibaek/.atom/packages/ava/lib/index.js:73
Hide Stack Trace
TypeError: Cannot read property 'getPaths' of undefined
    at Object.runAll (/Users/sunkibaek/.atom/packages/ava/lib/index.js:73:31)
    at atom-workspace.<anonymous> (/Users/sunkibaek/.atom/packages/ava/lib/index.js:16:62)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom Beta.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at CommandPaletteView.module.exports.CommandPaletteView.confirmed (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/command-palette/lib/command-palette-view.js:183:32)
    at CommandPaletteView.module.exports.SelectListView.confirmSelection (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/atom-space-pen-views/lib/select-list-view.js:338:21)
    at space-pen-div.atom.commands.add.core:confirm (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/atom-space-pen-views/lib/select-list-view.js:109:19)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom Beta.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:580:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom Beta.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:388:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/window-event-handler.js:98:36)
    at HTMLDocument.<anonymous> (/Applications/Atom Beta.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

It used to work fine so I have no idea what has caused this. Any ideas? Thanks!

Atom version is 1.10.0-beta0 although the error started to happen before 1.10.0.

NODE_ENV is set to test by this plugin, but it's not possible to add our own environnement variables. This could be helpful on some ALLOW_CONFIG_MUTATIONS=true cases with the config npm module (for example).

Thanks for the great work anyway ^^.

An awesome idea, from avajs/ava#183, is to run and see the result of a test run directly in the editor. And ability to quickly run the test your cursor is in, in the test file. We could even show the result of tests in the gutter, like linting. Now that we also support watching in AVA, this brings excited possibilities.

Prior art

• https://github.com/jacobmendoza/rspec-tree-runner
• https://github.com/wallabyjs/atom-wallaby
• https://github.com/boogie666/atom-mocha
• https://github.com/gedaiu/tested-atom
• https://github.com/paulpflug/mocha-ui
• https://github.com/TabDigital/atom-mocha-test-runner
• https://github.com/tswaters/atom-mocha-runner
• https://github.com/nguyenchr/atom-cargo-test-runner
• https://github.com/nathansobo/atom-jasmine-runner/
• https://github.com/klorenz/nuclide-test-runner-pytest

Anyone interested in helping out with this?

Assertions: https://github.com/sindresorhus/ava#assertions
Docs: https://atom.io/docs/latest/using-atom-snippets

I'm thinking the prefix should be t<name>, so tis, tsame, etc.

Could be easily adapted from the Sublime plugin if avajs/sublime-ava#1 is closed before this one.

The shortcuts use A not R

In a project, choose the Ava: Run command in the Command Palette or press Ctrl Alt R to run the tests. Choose Ava: Run File or press Ctrl Alt Shift R to only run the current test file. Press Esc to close the AVA panel.

I included what I thought would be useful, but could use some feedback on it.

https://github.com/sindresorhus/atom-ava/blob/master/snippets/ava.json

Anything missing or something that could be improved? (Assertion snippets are planned #1).

Relevant Sublime plugin discussion: avajs/sublime-ava#4

Would be nice to have test and assert completions. E.g. typing t. inside a test would show all assertion methods.

Docs: https://github.com/atom/autocomplete-plus/wiki/Provider-API

Inspiration: https://github.com/atom/autocomplete-plus/wiki/Autocomplete-Providers and https://github.com/jadb/atom-codeception-snippets/blob/master/scoped-properties/codeception-snippets.cson

When I hit CTRL+ALT+A, then 0 Tests will passed. With one test file open and SHIFT+CTRL+ALT+A works fine.

Found out, that happens since my project is symlink folder... when i 'cd' into the original folder it works.

Looks like these issues ricardofbarros/linter-js-standard#144

I have big plans for this, the Sublime plugin, and the VS Code plugin. Snippets are only a start.

An awesome idea, from avajs/ava#183, is to run and see the result of a test run directly in the editor. And ability to quickly run the test your cursor is in, in the test file. We could even show the result of tests in the gutter, like linting. (Let's discuss this thing in #3).

Let's do a brainstorming of what other useful things an editor plugin could do.

// @vdemedes @jamestalmage @kevva @sotojuan @novemberborn @ariporad @SamVerschueren

It looks a bit over-engineered and Atom already ships with an API for this: https://atom.io/docs/api/v1.7.3/BufferedNodeProcess

Would be a nice feature.

Maybe out of scope, but would be cool to show the status (open/closed) of the issue too.

Blocked until avajs/eslint-plugin-ava#110 is resolved.

Right now we manually create a right-pane to show the test results, but it would be much easier and user-friendly to take advantage of this new API. It's still in beta though.

http://blog.atom.io/2017/04/12/atom-1-16.html
http://blog.atom.io/2017/05/23/docks-deep-dive.html

Due to restrictions in our build pipeline we are installing all modules locally.

To avoid running into version mismatches, it would be great if the local version ./node_modules/.bin/ava could be preferred over the global.