Karma doesn't start server in browsers
See original GitHub issueI’m having a problem where karma never actually starts the server. It seems to start the browsers, but never the server. I’ve tested in Chrome, and after it’s launched the http://localhost:9876/
never loads. Running on windows 8, and node 0.10.33
The weird part is, I have the same exact configuration for grunt-karma, and it works no problem.
I get the error below:
INFO [karma]: Karma v0.12.28 server started at http://localhost:9876/
INFO [launcher]: Starting browser PhantomJS
INFO [launcher]: Starting browser Chrome
WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
WARN [launcher]: PhantomJS was not killed in 2000 ms, sending SIGKILL
WARN [launcher]: Chrome was not killed in 2000 ms, sending SIGKILL.
Here is my package.json for karma
"karma": "^0.12.3",
"karma-chrome-launcher": "^0.1.3",
"karma-coverage": "^0.2.1",
"karma-jasmine": "^0.1.5",
"karma-ng-html2js-preprocessor": "^0.1.0",
"karma-phantomjs-launcher": "^0.1.4",
Issue Analytics
- State:
- Created 9 years ago
- Comments:30 (6 by maintainers)
Top Results From Across the Web
Troubleshooting - Karma test runner
The --no-single-run option causes the server to print a URL and wait. Open the URL in a browser and use the browsers devtools...
Read more >Karma not running unit tests due to "No captured browser ...
This error can mean that the browser can't find the server. Check if you can reach the server at the URL it mentions....
Read more >Karma launch configuration does not allow passing command ...
I when I start karma runner and I want it to auto launch dartium browser in assert/checked mode and have it auto capture...
Read more >How to debug karma-based unit tests in Chrome or Firefox
The other thing that seems odd is that it doesn't seem as if the unit tests are being executed. The browser starts up,...
Read more >Faster Karma test runs that work in VSTS with Chrome ...
Because Karma doesn't care what test framework, assertion library, ... on the build server, and the new-ish Chrome headless browser sounded ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m having the same issue on debian:
Did anyone solve this?
I encountered the same issue. What helped me:
node_modules
folder completely.npm install
.Apparently karma files got corrupted and couldn’t be fixed automatically.