Karma is skipping all tests in project.

[jitindhillon-ms]

Hi,

Having trouble getting this extension configured in our angular project. After installing it can successfully discover the majority of the tests, but trying to run any just ends up skipping all of them. I'm struggling to figure out why. Any help would be appreciated. Attached is our karma.conf and the server log.

karma-server log (core-app).txt
karma.conf.txt

[lucono]

I'm not sure why that might be happening. The extension relies on Karma to run the tests, and only reports the results in the VSCode UI. If there are no focused tests and the tests themselves are not disabled but are being skipped, that indicates that Karma is skipping the tests. I would take a look at the project's setup or perhaps the execution environment.

[jitindhillon-ms]

I went and compared the karma config output from running ng test in our project vs the karma test explorer and the only notable difference is the babel-webpack section here:

I'm assuming this would affect running tests? Any suggestions on how to correct the config?

[jitindhillon-ms]

@lucono After further debugging, its seems to be related to the grep command the test explorer is sending to karma.

Once the server is up and running, I can send a manual command and the tests will run and the test explorer will reflect the success status:

However, the grep command that the test explorer sends doesn't match up with any tests, does it not like the regex?

[lucono]

That's interesting as both those grep values should capture those tests, the difference being that the one used by the extension anchors the filter to the beginning of the test names.

I would check using a separate minimal project to see if you're able to get any tests at all to run in VSCode using the extension, and that you don't have any extension settings or environment settings that may cause the regex attributes of the grep value to not be interpreted as expected.

[jitindhillon-ms]

Looks like we had an outdated karma-jasmine package, issue is resolved after updating.