Improve assertion messages when running expectations

[notanengineercom]

Showcases a draft on how to improve the readability and developer experience when evaluating assertions (received didNotReceive). Originated from the suggestion in #140, with this addition, we'd be recording stack traces of where a call was made. I also tried to enrich the assertion failure description with information like what has been called, how and what's expected:

Closes #140 Closes #27 Closes #138

[notanengineercom]

Tests for node.js 12, 14 and 16 fail just because the formatting of stack traces lines are slightly different than in the newer node.js versions (>= 18).

[ffMathy]

Wow, this is an amazing addition! I am currently sick and have been for a week, but hope to contribute at a faster pace soon ❤️

[ffMathy]

Yeah let's just drop support for those older versions of node BTW.

18 and up should be fine.

[notanengineercom]

Thanks 😄 Alright, what do you think about following node.js' release schedule? That would mean (looking at April'24), we'd run the CI tests against versions 18, 20 and 22. Get well soon 🫶🏼

[ffMathy]

Thanks 😄 Alright, what do you think about following node.js' release schedule? That would mean (looking at April'24), we'd run the CI tests against versions 18, 20 and 22. Get well soon 🫶🏼

I love that strategy! Let's do that :heart:

Thank you!

[notanengineercom]

I made some changes to allow a bunch of serialization options:

• using console.log
• using JSON.stringify
• getting a primitive from substitute

It just generates a string with a simple tree of the substitution object (not exposing any internals)