Unable to run igniteui-angular tests

[Aleksandyr]

Description

Unable to run igniteui-angular tests

• igniteui-angular version: latest
• browser:

Steps to reproduce

1. Remove node_modules and package-lock.json
2. Rebuild all dependencies
3. run npm run test:lib

The following error appears:

[rkaraivanov]

@Aleksandyr
Do you have karma-coverage installed? Try running it after a clean npm install.
Alternatively, does ng test igniteui-angular fails too?

[Aleksandyr]

@rkaraivanov I have karma-coverage installed.
I have tried plenty of things and the actual command fails. Alternatively, the suggested ng test igniteui-angular works.
But this does not fix the actual issue.

[rkaraivanov]

@Aleksandyr
Seems there was a change of how coverage is handled in the karma configuration for Angular tests with v11.
See this for additional info.
The ng test <library-name> work as that runs it without coverage enabled.
Moreover since we don't use npm run test:lib in our CI because we combine the coverage from the different jasmine tag runs, we did not catch it.

As a fix, you can copy the configuration from any specific other karma configuration file and remove the specific jasmine-spec-tags section.

@nrobakova
What are your thoughts on this issue?
Should we even have this npm script command as it seems it is barely used at all and the coverage is currently generated though other means?

[nrobakova]

@Aleksandyr and @rkaraivanov,
We have a definition to run the tests without coverage:
test:lib:watch
If you want I can create a similar to grid, hgrid, etc:
test:grid:watch
test:hgrid:watch
test:others:watch
test:tgrid:watch

[Aleksandyr]

@rkaraivanov @nrobakova Sorry for rising that flag so high. I thought that it's the main command for the CI.
@nrobakova There is no need of adding such commands, at least for me. We have enough.
But as a fix we should either remove the command or at least refer to the main karma.conf.js file and add that karma-coverage plugin or as @rkaraivanov proposed removing jasmine-spec-tags section?

[github-actions]

There has been no recent activity and this issue has been marked inactive.

[radomirchev]

@Aleksandyr is the issue still reproducible?

[Aleksandyr]

No, it is not. I'm closing the issue.