Support Non CLI Based angular projects

[raagh]

Support Non CLI Based angular projects

[subramn]

Thank you so much and issue is resolved.

[subramn]

any luck on this?

[Raagh]

Not yet. I am trying to support multi root workspaces on cli projects. After that I will move on to this :). If you need it very bad please feel free to contribute to the project. I will answer any questions you have for me, if not no problem. I will tackle it after the other open feature request

[Raagh]

@subramn do you have an angular non cli project I could use as example? I don't know how tests are run if there is no cli to actually do ng test and run de angular-dev-kit. Are just karma tests? please if you could provide me with an example it would be awesome for me to develop this feature.

[subramn]

Sure. i will upload a working solution by today.

[Raagh]

@subramn thanks :), I am doing some refactorings needed to implement multiple type of servers, hopefully it will make the implementation of this feature much easier.

[subramn]

I am attaching a solution, please extract and do npm install
Angular8-Template.zip

[Raagh]

Okey I see the structure now, so it is as I thought. Basically it means adding support for standalone karma cause when you do wanna test you just do karma start. Okey I will get to it, will let you know when its released. Thanks for the help and feedback @subramn ! 💯

[subramn]

any luck?

[Raagh]

still working on it. you can follow progress on this branch https://github.com/Raagh/angular-karma_test-explorer/tree/feature/support-standalone-karma

[Raagh]

@subramn just released version 0.3.0 with support for standalone karma and non cli projects. Just setup projectType as "Angular"/"Karma" and the path for the karma.conf.js based on the project folder and it will work just fine. I used your project as test during development.

Please let me know if you face any issues! enjoy :)

Also from now on there is an Azure pipeline for packaging and publishing new versions when something is pushed to master, this should make my releases a lot more frequent

[subramn]

Thanks. i have updated settings.json with project type and conf path
"angularKarmaTestExplorer.projectType": "Angular",
"angularKarmaTestExplorer.karmaConfFilePath": "."

is something i am missing.

[Raagh]

The default value for karmaConfFilePath is karn.conf.js, if the file is in the root of the project you re supposed to leave it as it is.

[subramn]

Ok thanks. do i have to create a settings.json specific to project and setup this
I have updated the settings.json for vscode
"angularKarmaTestExplorer.debugMode": true,
"angularKarmaTestExplorer.projectType": "Angular",
"angularKarmaTestExplorer.karmaConfFilePath": "karma.conf.js"

No luck yet

[Raagh]

Hi, please be sure to be on version 0.3.2 I published a few minutes ago. I had some issues with the azure pipelines and 0.3.0 was corrupt. I just tried your template with 0.3.2 and this as configuration in a separate settings.json file inside the project structure projectRoot/.vscode/settings.json "angularKarmaTestExplorer.projectType": "Angular", "angularKarmaTestExplorer.karmaConfFilePath": "karma.conf.js" and it loads fine.

sorry again for the problems, hopefully now it works as expected :)

[subramn]

I tried again and now the tests show up , but not able to run them.

[Raagh]

Change the name of the tests, the test explorer doesn't support two tests with the same name in the same folder structure( the name and the folder structure is used as an ID for running single tests and displaying errors, in this case the ID of both tests would be AppComponent should create app), that's why you see that warning icon.

I am glad that everything is working now!. Thanks for following on this feature. If you encounter any new bug please feel free to create a new bug report.

Thanks

[Raagh]

@subramn awesome news! hope you enjoy the extension.