TypeScript-Babel-Starter | sample setup using Babel CLI to build TypeScript code | Build Tool library

Unfortunately, I cannot provide an actual solution to your problem, but I think I examined its cause: See end of answer for a workaround.

The Node.js executable hides its options from the executed JS file. So if you run node --inspect file.js, the process.argv array will be ['/path/to/node', '/path/to/file.js'], without the --inspect flag appearing anywhere.

Electron however will not do the same. The process.argv array differs between node_modules/.bin/electron file.js and node_modules/.bin/electron --inspect file.js.

Jest seems to take all arguments from the third onwards and use them as its own options. That means, when you run node_modules/.bin/electron --inspect node_modules/.bin/jest, Jest will use the node_modules/.bin/jest argument as a test file pattern — and not find any that match it. That's also why your test output states: Pattern: node_modules/.bin/jest - 0 matches.

EDIT:

I found a terribly inelegant workaround, but it solves the problem.

You can create a "proxy" file which removes the --inspect argument from process.argv and run your tests through that: