Remove Jest as the test runner
This is driven partially by #24 (closed) making Jest not viable for the npm module installation, but also to expand the feature set to include the requirements below.
If there's another out there that can meet the desired needs as shown below, then look at those options, but so far none have been found so likely need to build a simplified test runner. Features should include:
- tests are of type pass/fail as well as complete/incomplete (#47)
- failed/incomplete tests should return a non-zero exit code
- both types should have the equivalent of "passed with warnings" with exit code 0 (#44 (closed))
- test failure does not include a stack trace (since the test code is not relevant)
- tests should have the ability to aggregate supplemental data (arbitrary as returned by the test)
- test framework provides reporting capability in multiple possible formats (e.g. html, json, console) - see #25 (closed)
- tests can be disabled by configuration settings
- test framework aggregates results from the test functions (per test, and a summary)
Edited by Aaron Goldenthal