Running karma on windows 8 throws the following error when trying to run in browser:
IE 11.0.0 (Windows) ERROR
You need to include some adapter that implements __karma__.start method!
Reproduce:
@Hacklone did you npm install karma-ie-launcher? Can you include your karma config file here please.
I'm not sure if I got it right (how start and run can work), but I first start running start without a config:
karma start config
(if I add --no-auto-watch then it wont't try running the not existent config)
Then I try to run this:
karma run karma.conf.js
According to karma run --help this should load the configuration file and it looks like that too, but it doesn't:
config - Loading config karma.conf.js
Chrome 34.0.1847 (Windows 7) ERROR
You need to include some adapter that implements __karma__.start method!
If I start karma with a config and the run it with an other config, the first config will run again.
What I'm trying to do is start a server with browsers attached to it and then run several configs. start --single-run does not always capture all the browsers
@Hacklone you did not answer my questions ;)
:) no I did not install it.
config file:
@Hacklone your original error is because you didn't specify any testing framework.
Do you still have this problem?
Actually my problem is that when running karma run with a config file it says that it's loading the config file, but it doesn't change the config file the karma start was started with.
I'm not sure if it's supposed to that that, but in that case the logging is very missleading.
Oh, that means we need to update docs. karma run does not reload the config file - it only triggers the run.
I agree that this is kind of confusing, but when you pass config file to karma run, it only uses it to figure out on which port is karma listening...
Yeah, tough it would be extremely helpful, so on a distributed (several agents) build server, we should only run one karma server not loads :)
karma run could post the config url to the karma server that could load the new config file, I think it would help a lot as single run with webdriver breaks a lot because of the webdriver, but if we could start the server, connect the browsers and then just run different configs, this problem would be solved.
@Zacknero What is your problem?
@Hacklone @vojtajina @sylvain-hamel What's the status of this issue?
Thanks
@maksimr Sorry I had a problem with Karma that gave me throwing error but I made some configurations with WebStorm and now it works. Sorry for the pointless post !! Lho removed!
@Zacknero currently when using webstorm and running some tests with jspm framework (karma-jspm) I'm getting the error You need to include some adapter that implements __karma__.start method! as well.
But that's not before I needed to change the working directory from within karma.conf.js file for being able to load some dependencies in the first place (e.g. es6-module-loader.js and such).
maybe you could share what you had to configure in webstorm to get it working.
Hi,
I'm absolutely new in making JS testing. So I followed this tutorial:
https://netbeans.org/kb/docs/webclient/html5-js-support.html
...to setup karma for netbeans in order to run karma from netbeans 8.
The karma server seams to be running fine:
WARN [karma]: Port 9876 in use
INFO [karma]: Karma v0.12.24 server started at http://localhost:9877/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 38.0.2125 (Windows 8.1)]: Connected on socket CtLwW0nR0JLISn1c3I22 with id 87368674
But when I run the test, I get this message:
No tests executed - perhaps an error occured?
Full output can be verified in Output window.
and the following error:
Chrome 38.0.2125 (Windows 8.1) ERROR
You need to include some adapter that implements __karma__.start method!
I have no idea, how to debug this! :-/
//update: The error disappears, after copying the karma.config to the npm base directory.
It seams, that karma@netbeans does not work with config on different places, even if I have defined this config (see step 9 in this tutorial: https://netbeans.org/kb/docs/webclient/html5-js-support.html)
I just run into this error. To a complete newb (like me!) that error message might as well have read:
Your computer says NO.
How about we suggest that the user should regenerate their karma.conf.js? Or, tell them that they need to stick something relevant in framework: [...]
Most helpful comment
I just run into this error. To a complete newb (like me!) that error message might as well have read:
Your computer says NO.How about we suggest that the user should regenerate their
karma.conf.js? Or, tell them that they need to stick something relevant inframework: [...]