Closed andrew-luhring closed 9 years ago
I have the same issue as well. I have to deactivate the reporter to make it work
I got the same issue whit that reporter, on Windows with Chrome version 36. This seem to affect only Chrome because the test I done on IE and Firefox work well.
This crash is the only reason why I dont use this reporter because his output format is awesome.
I got the same error using PhantomJS. This error goes and comes back if I update a NPM package or change a node_module file. It seems to go away if I change browsers in karma config to another browser, run grunt karma, and then change back to what I had before.
After some investigation the error happens in onBrowserComplete method when browserResults is an empty object even though the browser argument is not. var browserResult = browserResults[browser.id];
returns undefined. The reference to browserResult.results in the next line causes the error.
The question is why browserResults has no browser assigned to it event though browser is not empty.
I am using the version "0.2.4".
This has been fixed in 0.2.6
Example:
Also crashes if an extra }, ) function, var f = ; etc. All small errors. Karma does not crash if this reporter is disabled. Just a heads up.