-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multiple browser coverage #36
Comments
Sending reports for multiple browsers has been part of the roadmap, but I haven't found a way to do it. If you have suggestions, PRs welcome |
@caitp What is your idea how to implement this? However, unfortunately I don't use coveralls.io anymore. Currently I'm experiencing with codacy coverage. Btw: In my opinion you should point this out in the readme. This is essential for cross-browser tests. |
Looking at the coveralls API, it may be possible to have multiple coveralls jobs for the same source digest. If I get some time this week, I'll see if I can take advantage of this in a useful way (or, you're welcome to give it a try too). Short of that, I think we'd have to talk to Coveralls directly about supporting this use-case. |
I hear you man :( (sorry for the late response) |
I'm asking myself what happens when karma-coverage generates coverage reports for multiple browsers!? Coveralls.io always shows the coverage for the last tested browser. So I'm assuming that this reporter either sends all reports or just the last one. But it would make more sense to just send the average value of all tests.
@caitp what do you think?
The text was updated successfully, but these errors were encountered: