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
I just started to use the coverage-feature.
Unfortunately our test-pipeline increased dramatically concerning runtime, which makes it pratically unusable as the feedback-loop to the dev is way to long.
Without coverage:
With coverage:
I was wondering, if there is a way to only test the coverage for changed files. I know, that this is something that can be done with jest (which is not natively supported here) but not sure if I can somehow also configure it for the web-test-runner
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi everybody,
I just started to use the coverage-feature.
Unfortunately our test-pipeline increased dramatically concerning runtime, which makes it pratically unusable as the feedback-loop to the dev is way to long.
Without coverage:
With coverage:
I was wondering, if there is a way to only test the coverage for changed files. I know, that this is something that can be done with jest (which is not natively supported here) but not sure if I can somehow also configure it for the web-test-runner
Beta Was this translation helpful? Give feedback.
All reactions