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
Description
After running very_good test ... --coverage -r there's no easy way of creating a single coverage report with the lcov files that were generated.
Would be great to have a new option to generate a single HTML report file whilst the tests are running and be able to open (manually or automatically) the report afterwards.
Steps To Reproduce
Run very_good test ... --coverage -r
The command generates LCOV files inside each package of the app
There's no in-CLI way to merge them together in a single coverage report file
Expected Behavior
Run something like very_good test ... --coverage **--report** -r
The command generates a single report with all LCOV files generated in each package
Can be opened by simply running open coverage/index.html or having another command option --coverage-open, which does both things (generating and opening) 🤔
Additional Context
Would be great to see (if possible) the HTML report file as:
lib
packages/api_client
packages/app_ui
packages/user_repository
...
So we can have the whole coverage of each package in the first page, and then tapping on each of those bullet options we can navigate to the coverage of that package.
The text was updated successfully, but these errors were encountered:
alestiago
changed the title
fix: Include a command to generate a single coverage report for multi-package apps
feat: Include a command to generate a single coverage report for multi-package apps
Sep 22, 2023
Description
After running
very_good test ... --coverage -r
there's no easy way of creating a single coverage report with thelcov
files that were generated.Would be great to have a new option to generate a single HTML report file whilst the tests are running and be able to open (manually or automatically) the report afterwards.
Steps To Reproduce
very_good test ... --coverage -r
Expected Behavior
very_good test ... --coverage **--report** -r
open coverage/index.html
or having another command option--coverage-open
, which does both things (generating and opening) 🤔Additional Context
Would be great to see (if possible) the HTML report file as:
So we can have the whole coverage of each package in the first page, and then tapping on each of those bullet options we can navigate to the coverage of that package.
The text was updated successfully, but these errors were encountered: