Isomorphic Test Runner

[dalssoft]

What is the problem this feature will solve?

Currently I'm developing a library that runs both on node.js and on the browser and I would like to use node.js native test runner. However, I won't be able to use it because it only runs on node.js.

What is the feature you are proposing to solve the problem?

It seems that it is possible to run the test runner in the browser, as a quick look at the code, it seems to me that it is just javascript code (no native code) and no specific node dependencies.

I can think of a few alternatives:

• Create a new package that runs on the browser and node.js.
  pros: one package for both environments. also make node.js more useful for isomorphic libraries.
  cons: it will be a new package that the core depends on. Also, new requirement to make it work on the browser.

• Create a new package that runs on the browser and mimic the node.js test runner.
  pros: no dependency on the core.
  cons: two separate codes to maintain.

What alternatives have you considered?

Mocha: runs on the browser and node.js, but it is not TAP compatible. Also, depends on changing global variables.
Jest: runs on the browser and node.js, but it is not TAP compatible. Also, depends on changing global variables.
Tape: runs on the browser and node.js, but it has not the same authority as node.js test runner.
Ava: runs on node.js, but not on the browser (experimental).

[richardlau]

node:test was ported to userland in https://github.com/nodejs/node-core-test
On npm: https://www.npmjs.com/package/test
I believe it's manually synced to the code in nodejs/node: https://github.com/nodejs/node-core-test/wiki/How-this-repo-is-mantained