Skip to content
This repository has been archived by the owner on Oct 10, 2021. It is now read-only.

Allow pipelining coverage data from browsers #217

Open
bitinn opened this issue Jun 19, 2015 · 3 comments
Open

Allow pipelining coverage data from browsers #217

bitinn opened this issue Jun 19, 2015 · 3 comments

Comments

@bitinn
Copy link

bitinn commented Jun 19, 2015

When we need to report coverage data to a third-party service, such as coveralls, we would like to rely on zuul command to pipe us the coverage result from our sauce labs tests (allow us to specify which browser's test result to use, for example.)

Currently we have to install mochify in addition to zuul, in order to use phantomjs to run the same tests to produce coverage result.

And for one of my project, vdom-parser, this becomes a problem because we rely on DOMParser API in browsers, which phantomjs only has partial support.

So we ended up needing polyfill for DOMParser API, and because it's not spec compliant, we are unable to achieve 100% test coverage, even though on supported browsers we do have 100% coverage.

TL;DR: follow up on #174, please help us to get coverage data from real browsers and allow us to pipe them to coverage reporting services.

@bitinn bitinn changed the title Allow pipeline coverage data to provide CI coverage support on native browser Allow pipelining coverage data from browsers Jun 19, 2015
@cesarandreu
Copy link

Since you wanna get code coverage from the tests running on the actual browser (and not phantomjs), can't you hit the http://localhost:58700/__zuul/coverage/download endpoint?

@bitinn
Copy link
Author

bitinn commented Jul 30, 2015

I can try, to pull stats archive using curl and then unzip it and then pipe it to coveralls. Not sure if it would work on sauce labs though.

@defunctzombie
Copy link
Owner

I would review a PR or other improvements to make this work for you and other users. I don't recall the details of the coverage additions but if something is missing we can add it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants