kava
kava copied to clipboard
bevry
Kava has been powering accurate test suites in node.js and the browser since 2012.
Until someone has an issue with it, I'm probably going to leave it.
Now that the ESNext conversion is done, perhaps we can revaluate a lot of how we did things
Currently browser testing is performed manually. Certain things like displaying errors accordingly differ based on browser vs console (console reporter outputs them on suite or test finish if browser, can't...
Should the global suite have destroyOnceDone enabled or disabled? This should allow exit to correctly fire on browser environments, where no `process.exit` is emitted - however, it may already do...
Looks like whatever constructs the path to alternative reporters is incorrectly including 'console': ```console $ KAVA_REPORTER=console node -e '(require("kava")).test("must pass", () => true)' must pass must pass ✔ 1/1 tests...
Allow tests to return promises instead of calling callbacks Depends on https://github.com/bevry/taskgroup/issues/25 which once implemented, should be as easy as upgrading the TaskGroup dependency and writing verification tests.
Kava already accomplishes these goals of Deno - https://github.com/denoland/deno/issues/7330 - https://github.com/denoland/deno/discussions/10771 So all that would need to happen is providing a Deno compilation target.
Migrated from https://github.com/bevry/joe-reporter-console/issues/2