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
Which scope/s are relevant/related to the feature request?
vitest-angular
Information
When switched to Istanbul from V8 as coverage provider our tests stopped passing.
Vitest started generating different snapshots when one of component gets function as its input.
Describe any alternatives/workarounds you're currently using
Don't try serialize functions when creating snapshots
I would be willing to submit a PR to fix this issue
Yes
No
The text was updated successfully, but these errors were encountered:
I tried the things described here https://marmicode.io/blog/angular-template-code-coverage-and-future-proof-testing and found inconsistent behaviour, resulting in a different snapshot on each test run. So I'm reporting this and asking for a new feature. In my project, I have switched back to V8 as the coverage provider because I cannot leave the project with a broken test suite. I'm seeing a lot of power and new capabilities in Vitest. It will take some time for the integration to mature. But the future looks bright.
Which scope/s are relevant/related to the feature request?
vitest-angular
Information
When switched to Istanbul from V8 as coverage provider our tests stopped passing.
Vitest started generating different snapshots when one of component gets function as its input.
Describe any alternatives/workarounds you're currently using
Don't try serialize functions when creating snapshots
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: