Activating extension 'raagh.angular-karma-test-explorer' failed: Cannot find module '..../.vscode/extensions/raagh.angular-karma-test-explorer-0.3.0/out/main.js'. about angular-karma_test-explorer

[Raagh]

Hi, thank you for reporting this bug. Are you opening the project folder in vscode or opening a root folder that contains multiple projects? Are you using open folder or open workspace? do you have other test explorers?(if yes which one?) sounds stupid but did you try uninstall/install again?

just tried it with the version uploaded to the marketplace and works fine on windows and mac.
yesterday it was the first release using azure pipeline for package and publish so I was wondering if that messed up something, but it has to be something else.

[aavelyn]

It's a single project.

1. ng new test
2. install your vscode plugin (all other test-explore plugins deinstalled before)
3. reload vscode

I also noticed that the default karma.conf.js path is just "karma.conf.js" from Root while a cli created angular project put it to root/src/karma.conf.js

[Raagh]

No worries, the karma.conf configuration it's only used on karma/angular projects. With angular cli projects everything is get from the angular.json or angular-cli.json.

Another stupid question, did you do npm install on the project?
If you run Ng test from the project the tests run?
In vscode you re opening the root folder of the project?( where the angular.json is located ).

I am gonna run an Ng new and check if I missed something with latest versions of the angular cli.

I will report back here after.

EDIT 1: I was able to reproduce the bug with a new project. I will check whats going on, to be honest I have no clue. Please still make sure that you do npm install on the project and that ng test works.

EDIT 2: for whatever reason vsce package is ignoring my out folder(which contains the compiled source) when I package on windows. It works fine if I package on Mac OS, makes no sense

[Raagh]

@aavelyn just posted version 0.3.2 it should work fine, something in my azure pipeline is messing the package or the publish. I am not sure exactly which part. Its the same code just a version I packaged myself and published manually. Tried it on an regular cli project and its working

[aavelyn]

It works now thanks! Great Plugin!

Some things I've noticed:

• It took over 3min to initialize and load all the tests. (I have roughly 80)
• It would be great to have a folder view (see where the spec files are)
• It would be great to see the total amount of tests run/fail

Cheers!

[Raagh]

Really happy it works now and you like it!. last release was a problem, I need to step up on stability.

Totally agree it should'nt take that long to load, specially that 80 is not a lot of tests. One question on that matter, how long does it take when you run "ng test" from the project?

Great suggestions, I will consider them for future updates. Shouldnt be that hard to implement( I am still new on developing extensions though ahaha)