Run AVA as a REPL

[backspaces]

Description

I believe this is a feature request (or documentation)

I need to run node with the same environment as ava has for simple debugging of my test files.

Currently I believe I have to simply ava test/FooTests. But these sometimes fail and I need to know why by actually being in the node repl with the ava environment.

Test Source

None

Error Message & Stack Trace

None

Config

Copy the relevant section from package.json:

None

Command-Line Arguments

Copy your npm build scripts or the ava command used:

    "test": "ava"

Relevant Links

https://github.com/backspaces/as-core

Environment

git 2.15.0
node v8.9.3
npm 5.5.1
yarn 1.3.2
eslint v4.14.0
ava 0.24.0

[novemberborn]

There is a section on Debugging in the README: https://github.com/avajs/ava#debugging

To be honest I've never actually used that myself, but it should work. See also https://github.com/avajs/ava/blob/master/docs/recipes/debugging-with-chrome-devtools.md.

(I'm closing this issue, but please let me know if this helps you, or if I've misunderstood your problem.)

[backspaces]

Here's my goal: to somehow start an ava/node repl, in interactive mode. In other words somehow start node/ava, and be left in node so that I can try things within the ava-created environment.

What I mean by that is that I start node, then require('ava.js') and be left in interactive mode to try things just like when using node in interactive mode.

If I try: node --interactive --inspect node_modules/ava/profile.js I get Error('Specify a test file').

Or this node --interactive --inspect node_modules/ava/profile.js test/test.js it runs the tests, printing out

Debugger listening on ws://127.0.0.1:9229/005415cf-dc16-455b-bcc6-dc76cb96948f
For help see https://nodejs.org/en/docs/inspector
TEST: foo null
TEST: AS null
RESULTS: { failCount: 0,
  knownFailureCount: 0,
  passCount: 2,
  skipCount: 0,
  testCount: 2,
  todoCount: 0 }

but exits, not remaining in the repl.

How do I simply start ava/node in such a way it remains in the repl, in interactive mode?

[novemberborn]

Yea this isn't as easy at it should be. We do have #1505 open, but it looks like we should improve the documentation too.

This works for me:

// test/test.js
import test from 'ava'
debugger

$ node --interactive --inspect-brk node_modules/ava/profile.js test/test.js

Then if I open chrome://inspect I can target the profile.js process, press Continue and it'll break at debugger.

[backspaces]

OK we're getting there. I inserted debugger exactly as above. Then ran the node command:

node --interactive --inspect-brk node_modules/ava/profile.js test/test.js
Debugger listening on ws://127.0.0.1:9229/0a853d55-8246-46ce-b7c8-1d8d9001e3d3
For help see https://nodejs.org/en/docs/inspector
Debugger attached.

I then opened chrome://inspect which looked like this:

I clicked on the inspect link and this appeared:

By press continue, do you mean click on the blue debugger continue button?

When I do that I get:

That looks pretty hopeful! When I click on console I get:

But when I try to require my cjs rollup I get:

It does appear to be the right path, using others gives errors. And lots of node works, like using the process.cwd() & __dirname give the right values, and fs=require('fs') works fine.

So it seems like I'm in the wrong scope or something similar??

Thanks a LOT for your patience, a lot of this is new to me so I'm likely doing something silly.

[novemberborn]

I'd put the debugger in the test or source code that you actually want to debug. That way you can be sure everything is set up exactly as you need it to.