search

karma-runner / karma-chrome-launcher

A Karma plugin. Launcher for Chrome and Chrome Canary.
MIT License
469 stars 119 forks source link

Setting specFilter directly on Env is deprecated #190

Closed dotnetCarpenter closed 6 years ago

dotnetCarpenter commented 6 years ago

When I run tests now, I get the following:

HeadlessChrome 0.0.0 (Ubuntu 0.0.0) ERROR: 'DEPRECATION:', 'Setting specFilter directly on Env is deprecated, please use the specFilter option in configure'

For now it's ok. But one day it will probably fail.

dotnetCarpenter commented 6 years ago 
"jasmine-core": "^3.3.0",
"karma": "^3.1.1",
"karma-chrome-launcher": "^2.2.0",
"karma-coverage": "^1.1.2",
"karma-firefox-launcher": "^1.1.0",
"karma-jasmine": "^1.1.2",
abdelkrimdev commented 6 years ago

Hello!!! You have to update the karma-jasmine to the latest version 2.0.0 this will fix the issue. Thanks 😄

dotnetCarpenter commented 6 years ago

@abdelkrimdev Thanks, that works!

mowali commented 5 years ago

My karma-jasmine is set to latest 2.0.1 but still getting error. I just updated to Angular 7 and TypeScript 3.2 "jasmine-core": "^3.3.0", "jasmine-spec-reporter": "^4.2.1", "karma": "^4.0.1", "karma-chrome-launcher": "^2.2.0", "karma-cli": "^2.0.0", "karma-coverage": "^1.1.2", "karma-coverage-istanbul-reporter": "^2.0.5", "karma-jasmine": "^2.0.1", "karma-jasmine-html-reporter": "^1.4.0", "karma-trx-reporter": "^0.4.0",

proAppleEater commented 5 years ago

I'm in the exact same situation as mowali !

ovitrif commented 5 years ago

Same

rogeriopvl commented 5 years ago

@mowali @proAppleEater @ovitrif This issue is not related with karma-chrome-launcher. Please check: https://github.com/karma-runner/karma-jasmine/issues/221

shardulsonar commented 5 years ago

How to check the version of karma-jasmine ?

johnjbarton commented 5 years ago

Look in node_modules/karma-jasmine/package.json

lenichols commented 4 years ago

Updating Karma-Jasmine to 2.0.1 solved this for me. Thnks!

Yagnadat-Talakola commented 4 years ago

Thanks for raising the issue @dotnetCarpenter, I've had a similar issue today. Updating the version to 2.0.0 helped remove it.

johnjbarton commented 4 years ago

You probably want 2.0.1... but 3.0.1 is out.