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.

Sign up for GitHub

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

Jump to bottom

Decide recommended coverage approach #68

Open

lukeapage opened this issue Feb 10, 2020 · 1 comment

Assignees

Labels

Contributor

lukeapage commented Feb 10, 2020 •

edited

We have implemented outputting coverage per test by converting to istanbul, but there are problems so we need to decide approach.

We might also want to merge all v8 coverage and convert to istanbul once at the end.

lukeapage added enhancement P3 labels

lukeapage self-assigned this

Contributor Author

lukeapage commented Feb 22, 2020

2 problems:

this needs finishing and merging Add support for 1:many source maps istanbuljs/v8-to-istanbul#91
this needs addressing: Coverage merging is naieve and doesnt work if coverage is generated by v8 istanbuljs/istanbuljs#531
because it must be normal to want to combine unit test and automation coverage.

lukeapage changed the title ~~Code coverage using chrome coverage~~ Decide recommended coverage approach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment