It hasn't been discussed whether the data merge web interface will be developed in this repository. Since the web UI will very likely be developed using the infusion framework, if UI is a part of this repository, jqUnit from infusion will be the best choice. However, if UI is not part of this repository, pulling in 43M infusion library for testing a few node.js scripts seems an overkill. This evaluation is to determine in the latter case, what's the best choice for testing these node.js scripts.
Can test node.js scripts;
Support the test of asynchronous code such as Promise;
Simple and lightweight;
It would be a bonus if the testing framework supports browser tests, but this is not a must-have.
Needs to specify babel in package.json to support ES6 import/export. See this discussion.
Needs to install a plugin to transform ES6 to commonjs. See this discussion.
If this repository will contain UI code developed using infusion, the infusion testing framework is the best choice.
Otherwise, Jest seems to be the best choice.
The decision made at the tech check in meeting on 2020-11-12 is to use infusion node-jqUnit as the testing framework because fluid-testem built around jqUnit is an existing helper for producing the coverage report for combined node.js and browser tests.