Skip to content

Investigate client-side code coverage #22221

@LeeDr

Description

@LeeDr

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions