Unable to see tests in Test Explorer using

[harris-authors]

Unable to see tests in Test Explorer using

[harris-authors]

Thanks so much for the pointers. My problem was slightly different, but understanding what the extension was looking for from the target helped put me on the right track.

[callumcarolan-clevertech]

I am experiencing this issue also. tests run fine with ng test but do not show up in explorer and loading icon is permanently spinning. No output in terminal or extension log

[mbrechet]

Hi, same problem for me too. Is there a workaround ?

[callumcarolan-clevertech]

I have not found a workaround for this yet

[mbrechet]

As a temporary solution I use jest with Jest Test Explorer plugin and it works. I just had to modify my test launch configuration to be compatible.

[callumcarolan-clevertech]

@mbrechet What did you modify in the configuration?

[mbrechet]

Hi, I follow @ahasall tutorial to replace Karma by Jest and install Jest Test Explorer plugin :

https://www.amadousall.com/how-to-set-up-angular-unit-testing-with-jest//

I works for me with Angular 11

The files in the .vscode folder are only useful if you want to debug directly in vscode during your tests. I thnink, the plugin problem occurs before because we cannot run the tests.

[s4m0r4m4]

I've run into this as well. For me the issue was this:

1. This extension assumes the target to launch from the selected project is called "test" and that it has a "karmaConfig" option specified.
2. I had a Jest-based target called "test", which was being launched by the extension (it does not check to see if it is truly a karma-based test)
3. The extension does not have a timeout when waiting to connect to the karma test, so it just sits there indefinitely.

Make sure your default project (or the selected project, whichever you're using) has a target called "test" that launches your karma tests.

[callumcarolan-clevertech]

I've run into this as well. For me the issue was this:

1. This extension assumes the target to launch from the selected project is called "test" and that it has a "karmaConfig" option specified.
2. I had a Jest-based target called "test", which was being launched by the extension (it does not check to see if it is truly a karma-based test)
3. The extension does not have a timeout when waiting to connect to the karma test, so it just sits there indefinitely.

Make sure your default project (or the selected project, whichever you're using) has a target called "test" that launches your karma tests.

What are you referring to when you say "target"? Do you mean a command or entry point?

[s4m0r4m4]

In Angular parlance, targets are specific configurations that govern how the Angular CLI functions. So ng build is calling the build target of the Angular CLI. In a more practical sense - in the angular.json file, the targets are the keys within the architect object within a given project. So in the example below, build, serve, test-jest, and test are all targets for the angular project my-project.

"projects": {
        "my-project": {
            ...
            "architect": {
                "build": {
                    "builder": "@angular-devkit/build-angular:browser",
                    ...
                },
                "serve": {
                    "builder": "@angular-devkit/build-angular:dev-server",
                    ...
                },
                "test-jest": {
                },
                "test": {
               ....

You can read more here: https://angular.io/guide/workspace-config#default-architect-builders-and-targets

[callumcarolan-clevertech]

Wonderful thank you.

…

On Fri, Jan 22, 2021 at 8:43 PM s4m0r4m4 ***@***.***> wrote: In Angular parlance, targets are specific configurations that govern how the Angular CLI functions. So ng build is calling the build target of the Angular CLI. In a more practical sense - in the angular.json file, the targets are the keys within the architect object within a given project. So in the example below, build, serve, test-jest, and test are all targets for the angular project my-project. "projects": { "my-project": { ... "architect": { "build": { "builder": ***@***.***/build-angular:browser", ... }, "serve": { "builder": ***@***.***/build-angular:dev-server", ... }, "test-jest": { }, "test": { .... You can read more here: https://angular.io/guide/workspace-config#default-architect-builders-and-targets — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#96 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ7ZBNU2FAW4XMIKFFBDKJLS3HPPXANCNFSM4VR5LEXQ> .

[s4m0r4m4]

Glad to hear it. I've submitted a PR to help provide a little more visibility to when tests don't appear, but there's certainly more work to be done. What was your fix? Hopefully we can document more of these to help others too. If you have things working, you can close this issue too.