jest should not use forceExit but needs to call jest through node API

Open kenotron opened this issue 6 years ago • 2 comments

Currently, we trigger jest with a CLI interface. This is okay, but in order to have the CLI quite FOR SURE when all tests are over is through --forceExit. This unfortunately generates an ugly output, we need to either somehow filter that output or have jestTask call jest node api to trigger the runner.

Sep 10 '19 16:09 kenotron

need to call jest.runCli() api rather than spawn to trigger jest.

Oct 30 '19 03:10 kenotron

Issues seem to have gone stale.

Mar 07 '20 00:03 github-actions[bot]