Suggestion: Make it QUnit API

[izelnakri]

Summary

Hi there, I've just had a look into this project and I'm maintaining a different testing tool in node.js. I'll soon investigate moving the tool to deno. I've also read the blog post to see your motivation on building this tool. Thank you for building it, I might also use your code as reference/example.

I highly suggest that you move the library API to QUnit API: https://api.qunitjs.com/QUnit/module/#hooks-on-nested-modules . I suspect this achieves the same thing and would really help rest of the community to use a shared testing API/tools eventually.

Also, another suggestion: you can make the tool output in TAP - Test Anything Protocol by default so people can write their own custom reporters.

[crookse]

Hey @izelnakri , we appreciate you bringing this up! personally, I don't know much about qunit, but how would Rhum fit into it exactly? It seems that quint already has nesting, grouping, and hooks. I don't see mocking, but maybe i'm not looking in the right spot? anyways, if it's the mocking piece you're talking about, we're actually having an internal discussion about moving rhum forward as being a mocking module without a test runner. and possibly making it agnostic