Proposal: add transformation from TestMessage[] to marble string in TestScheduler

[jiayihu]

I'm trying to test a lib based on RxJS and I noticed that Developer Experience could be improved a lot. For instance this is the output using Jest matcher for deepEqual passed to TestScheduler.

Actually it's not that bad because Jest did a great work with diffs, but if you try instead assert.deepEqual from Node or other test runner matchers you get a much worse result.

To improve this situation in my testing I've created a small utility to convert from TestMessage[], passed to the matcher, back to a marble string. I think this could be done directly by TestScheduler and different test runners like Mocha, Jasmine or Jest could take advantage from it.

The current result is this:

You can catch the problems immediately or look at TestMessage[] for more granular info.

[kwonoj]

I'm closing this issue for now via umbrella issue #1775, I've been working to create new test interfaces but too busy, it's bit stalled. Once we have initial design for new impl we can discuss enhancements from there.

[jiayihu]

I think the issue should be kept open to since it's not solved and in #1775 there isn't any explicit point about it. Anyway thank you for your hard work on RxJS, I really don't have complains!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.