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
bazel coverage on a jasmine_test target should report lcov coverage just like js_test does :)
We should essentially see a bazel-testlogs/package/target/coverage.dat file with the lcov report for the test, and the combined lcov report in bazel-out/_coverage/_coverage_report.dat when running bazel coverage //package:target
The text was updated successfully, but these errors were encountered:
What is the current behavior?
It seems that
rules_jasmine
doesn't support code coverage viabazel coverage
like thejs_test
rule does.The
*.instrumented-files
file in the output tree always comes up empty. I think this is becauserules_jasmine
doesn't callcoverage_common.instrumented_files_info()
and return its provider likejs_test
does here: https://github.com/aspect-build/rules_js/blob/v1.37.1/js/private/js_binary.bzl#L571Describe the feature
bazel coverage
on ajasmine_test
target should report lcov coverage just likejs_test
does :)We should essentially see a
bazel-testlogs/package/target/coverage.dat
file with the lcov report for the test, and the combined lcov report inbazel-out/_coverage/_coverage_report.dat
when runningbazel coverage //package:target
The text was updated successfully, but these errors were encountered: