Review testing config for better coverage reporting #115
Comments
Westbrook
added a commit
that referenced
this issue
Aug 16, 2019
* Test of running tests with open-wc * Remove some deps * Try building the repo first * Massage test for CI * conncurent watching * Typing * Clean up deps. * Clean up deps. * Clean deps * Clean up * Custom coverage %s * Custom coverage %s * Update test waiting... * That entry does not do things, leave it as it was * Correct fixture type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behaviour
Test coverage can be easily acquired.
Actual Behaviour
Not sure how.
Reproduce Scenario (including but not limited to)
npm testgives pass fails, but no inline or output based coverage information.Current Idea
I'm not sure whether/how the junit reporting is actually being used in our CI processes. Investigate replacing it with @open-wc/karma-testing or extending from the open-wc config with the junit work. This should also reduce our direct dependency graph, which will make maintaining the repo easier long term.
The text was updated successfully, but these errors were encountered: