You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the test suite for this project only exercises collecting coverage from a dart application running on the VM. This does not cover collecting coverage from content-shell.
I bring this up because Travis CI always uses the latest version of Dart, but at times there's an issue with the version of content-shell that it uses for CI builds (see travis-ci/travis-ci#4406). If this package had tests to exercise content-shell coverage collection, those issues would potentially be caught by the CI build.
Agreed -- getting coverage tests against content_shell checked into the repo is definitely valuable.
Think we also need a separate (non-coverage-specific) global canary test that checks the recency and health of content_shell tests on Travis as per that issue.
Currently the test suite for this project only exercises collecting coverage from a dart application running on the VM. This does not cover collecting coverage from content-shell.
I bring this up because Travis CI always uses the latest version of Dart, but at times there's an issue with the version of content-shell that it uses for CI builds (see travis-ci/travis-ci#4406). If this package had tests to exercise content-shell coverage collection, those issues would potentially be caught by the CI build.
@cbracken @kevmoo
The text was updated successfully, but these errors were encountered: