Skip to content
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

Investigate client-side code coverage #22221

Closed
LeeDr opened this issue Aug 21, 2018 · 3 comments
Closed

Investigate client-side code coverage #22221

LeeDr opened this issue Aug 21, 2018 · 3 comments
Labels
Team:Operations Team label for Operations Team Team:QA Team label for QA Team test

Comments

@LeeDr
Copy link
Contributor

LeeDr commented Aug 21, 2018

Describe the feature: UI tests are slow and can be flaky so we should not add more of them unnecessarily. Having code coverage metrics could help us plan tests to get the right coverage.

Describe a specific use case for the feature: Here's some links about Istanbul tool that might be useful;
https://istanbul.js.org/

https://www.engineyard.com/blog/measuring-clientside-javascript-test-coverage-with-istanbul

https://medium.com/@the1mills/front-end-javascript-test-coverage-with-istanbul-selenium-4b2be44e3e98

@LeeDr LeeDr added test Team:Operations Team label for Operations Team Team:QA Team label for QA Team labels Aug 21, 2018
@LeeDr
Copy link
Contributor Author

LeeDr commented Aug 21, 2018

cc @silne30 @spalger @tylersmalley Maybe we could work together on this on a fix-it-friday?

@LeeDr
Copy link
Contributor Author

LeeDr commented Aug 21, 2018

@legrego says he's used Istanbul before

@LeeDr
Copy link
Contributor Author

LeeDr commented Jun 23, 2020

This is in place now. Closing.

@LeeDr LeeDr closed this as completed Jun 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Operations Team label for Operations Team Team:QA Team label for QA Team test
Projects
None yet
Development

No branches or pull requests

1 participant