Meta

[sindresorhus]

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

[vadimdemedes]

How about displaying (maybe in tooltip) actual values of variables in assertions via power-assert?

Example:

let actual = 'hello';
let expected = 'world';

t.is(actual, expected);

And on hover we display 'hello' over actual and 'world' over expected.

[sindresorhus]

@vdemedes That's a great idea!

[ThomasBem]

I think wallaby.js has some cool features in their VSCode extension.

wallaby.js VSCode extension

• Display line by line code coverage in editor
• Console.log output in editor in tests
• Re-runs affected tests and shows results right in editor
• Navigate to tests that cover a specific line of code

[jednano]

Here are some vscode/AVA features I'm looking for:

1. An AVA problem matcher. Apparently, you can create your own.
2. An AVA debugger extension. It's already been requested in a vscode issue, but they're saying it should be a debugger extension.
3. TypeScript support or at the very least a guide to show how to compile with tsc in the background while running the ava command in the foreground.

Note: I'm currently seeing a lot of garbage in my vscode AVA task. It looks like this: