Closed mnholtz closed 3 weeks ago
This will be nice, but given that we're working through the list of manual regression tests, the coverage of test cases/stores will be a better metric of coverage than code coverage. So I'd prioritize any blockers to testing over collecting code coverage
Here's a quick demo branch of generating initial code coverage. We would still need to figure out a way to generate coverage for pop-up pages like the sidebar and for the service worker. https://github.com/pixiebrix/pixiebrix-extension/commit/b0200ca0533b7c34644fa77c49c1070e1422fe74
This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.
This issue was closed because it has been stale for 7 days with no activity.
We'd like a way to systematically calculate code coverage from e2e tests to facilitate discussion around minimum test expectations.
Playwright doesn't seem to provide code coverage support out of the box: https://github.com/microsoft/playwright/issues/9208
Potentially useful resources: