If even 1 test fails, tests fail to load Test discovery failed: Process exited with non-zero status code 1 (Click to show log) about karma-test-explorer

[Charuru]

This bug seems to be new in 0.7, downgraded to 0.6.1 works fine.

[Charuru]

Actually do not need to go back so far, 0.7.3 works correctly.

[lucono]

@Charuru I'm not able to reproduce this issue with the latest version, 0.7.5. Can you create and share a minimal project repo that reproduces the issue?

[lucono]

Thanks @Charuru. I was able to reproduce the issue consistently with your sample project and when using the jsdom browser, and across all recent versions of the extension, including v0.7.3. I am not however, able to reproduce it with the extension default chrome browser for any of the recent extension versions, including the latest version and v0.7.3.

The issue seems to be with jsdom, where it fails when karma tries to trigger the initial test discovery /run request to fully populate the project tests into the test explorer view.

Are you able to reproduce the issue with Chrome, Firefox, or any other browser?

[Charuru]

@lucono Thanks for trying it, doesn't make a difference on my machine whether I use jsdom or ChromeCanaryHeadless. Same behavior.

[Charuru]

Also, if I click on "Retry Test Load" it will keep on erroring, but if I save the test and it autoruns then the explorer will populate correctly.

I don't know if this is useful information, but when I click on the refresh button on test explorer, I see the tests being runned, all the logs, etc are as expected, and the tests show up for a moment before disappearing in place of the error and then Failed to load tests - Test discovery failed: Process exited with non-zero status code 1. This is ChromeCanaryHeadless.

[Charuru]

Changing to HTTP from CLI fixed this too.

[lucono]

I see, thanks for the update. The karmaTestExplorer.testTriggerMethod setting is indeed experimental. In fact, its http option is stable, but the cli trigger method is actually what's experimental, so I'm not surprised that you ran into issues using that option.

Glad you were able to identify the issue.