Switch to tape or mocha/karma?

What do you think about switching from jest to tape?

I’ve got a preliminary setup here:

https://github.com/yisar/fre/compare/master...mindplay-dk:use-tape

This is unfinished - tape is much simpler than jest, but it doesn’t come with “batteries included”, so it takes more work to set this up.

For now, I have Babel with JSX and async support working - this seems already much safer, because I can clean up JS-DOM after each test, which means that timeouts get flushed, which means tape can catch assertions that run after the promise resolves. (the commented-out lines demonstrate this.)

I still need to set up code coverage and XML reporting for CI integration - before I can port the actual tests, so a lot of work left.

Do you think I should continue with this?

[mindplay-dk]

I see, so we can only test DOM in node, and then test scheduler through chrome panel in the future.

Well, it’ll run the full suite of tests - just that those tests will be effectively testing the integration with a bunch of mocks and stubs, whereas what we’re really interested in is integration with a browser.

But we’ll figure out later how to run the tests without the mocks and stubs. 🙂

[yisar]

If only performance is not supported, then polyfills can be found, and I don’t think js-dom is a good choice. We can refer to the practice of preact, multiple libraries are used at the same time.
Anyway, I don’t think jest is a good choice for testing js framework now.