Seems the "serializer" is added globally, maybe because we are not running <a href="ht

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Ah, found this <a href="https://github.com/facebook/jest/blob/main/packages/jest-snaps

Is <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id=

`expect.addSnapshotSerializer()` not working as expected about jest-light-runner HOT 5 CLOSED

nicolo-ribaudo commented on May 18, 2024

`expect.addSnapshotSerializer()` not working as expected

from jest-light-runner.

Comments (5)

SimenB commented on May 18, 2024 1

I think that's good. It might make sense for Jest to expose some sort of "reset serializers" API which reset the array to the default (happy to take a PR)? But with the current API I think your approach is good

from jest-light-runner.

fisker commented on May 18, 2024

@SimenB

Can you help me understand how addSnapshotSerializer works? Does expect.extend create a new instance? How to remove snapshot serializer or restore state?

In this Prettier PR, we use addSnapshotSerializer() in some test, but seems all tests using that.

I'm calling createExpect on each test, but not working as expected.

Thank you!

The failing test, that snapshot serializer replace \ to /

from jest-light-runner.

fisker commented on May 18, 2024

Ah, found this https://github.com/facebook/jest/blob/main/packages/jest-snapshot/src/plugins.ts#L39, so I can backup it and restore after test?

from jest-light-runner.

SimenB commented on May 18, 2024

Yeah, just module state. Which works fine in Jest, but caching probably messes up for this runner

from jest-light-runner.

fisker commented on May 18, 2024