enhancement: support for node:test snapshots

[boneskull]

Issue description or question

When running tests using Node.js' snapshot test facilities, I get the following two errors which do not appear when running tests from the command line:

Comparison with Node.js' assert module / deepStrictEqual / "to deep equal" / deepStrictEqual <snapshot>
Invalid state: Invalid snapshot filename.
TestContext.<anon> @ test/error/assert-error.test.ts:38:7 

Comparison with Node.js' assert module / deepStrictEqual / "to deep equal" / "to deep equal" <snapshot>
Invalid state: Invalid snapshot filename.
TestContext.<anon> @ test/error/assert-error.test.ts:42:7

The path to the snapshot file is test/error/assert-error.test.ts.snapshot, which both exists on disk and matches a files pattern in my Wallaby config.

If I had to guess, Wallaby doesn't support snapshot tests in node:test. This would then be a request to support them. 😄

Wallaby diagnostics report

Gist

Thanks for your work on Wallaby!

P.S. I'm seeing a "body is too large" error when attempting to paste the diagnostics file in; the issue template might need to direct issue creators to a different method!

[boneskull]

If you want a repo to play with, I have some snapshot tests in Bupkis

[smcenlly]

Thanks for raising the issue. When we initially investigated and added support for node:test, snapshots behavior was sufficiently different to other test runners that we weren't exactly sure how to handle and support them. So you're right in saying that they're not supported in node:test.

Have added as an enhancement request for our backlog.

Thanks for the sample repo!

[boneskull]

Regarding its snapshot implementation, it seems pretty straightforward insofar as serialization is concerned. It just performs JSON.stringify (custom serializers must return strings) on the value then dumps it in a CommonJS <filename-with-extension>.snapshot file where the exported name is the computed test name followed by an index (starting with 1). So exports['full test name 1'] = 'some string'. But perhaps this is not what you are referring to 😄

[smcenlly]

Thanks for the info! Going back some time, but IIRC the behavior difference was more about how they're scheduled and when the update vs. other testing frameworks when interacting with the API. It may well have changed since then (it's been a while).