-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
🛠️ Repo: Compute in-browser test coverage numbers #2883
Comments
I've been working on this in the Getting Coveralls to take reports from multiple build jobs in the same build turned out to be way easier than I thought. I wasted so many hours looking for a more complex solution because I didn't initially realize I could just apply After that, I looked into adding coverage to the browser runs. Here's what I found out.
Feel free to pull it down locally and experiment to confirm or deny any of the above and try to fix the bundle errors. |
(I should add that the |
Found and fixed what I'd screwed up; that branch is working now (modulo Sauce flakes), so I've submitted PR #2886 for it. |
We have coverage numbers, but only in Node.js. I'd like to see the coverage numbers against tests run with Karma.
Gathering coverage from Karma seems fraught with peril.
I would entertain other suggestions to improve how we run browser-based tests. My only requirement is that the tests run in a strict browser-like environment--
jsdom
shenanigans or Electron won't do.The text was updated successfully, but these errors were encountered: