sxy-test-runner 1.4.0 → 1.4.1

package/dist/cli/lib/runTests.js

@@ -67,7 +67,7 @@ export async function runTests(config, testFiles, failingTests, customOut = unde
     // wait for the output to complete
     await Promise.allObj(testRunOutPromises);
   });
-  await timeProfileAsync('show initial test run results', async () => {
+  return await timeProfileAsync('show initial test run results', async () => {
     const out = customOut ? async (...texts) => await customOut(...texts) : async (...texts) => await mainOut(...texts);
     const testsResultsSummary = {
       total: 0,
@@ -139,5 +139,9 @@ export async function runTests(config, testFiles, failingTests, customOut = unde
     }
     await out(chalk.orange`To do: account for tests with loading errors`);
     // out(``)
+
+    // full success?
+    // true/false gets returned to the caller of runTests()
+    return testsResultsSummary.itsPasses === testsResultsSummary.itsTotal;
   });
 }

package/dist/cli/once.js

@@ -31,10 +31,13 @@ export async function once() {
   const {
     runTests
   } = await import('./lib/runTests.js');
+  let exitCode = 2;
   if (testFiles.length > 0) {
     await log(chalk.brightblue`running tests...`);
-    await runTests(config, testFiles, []); //// async function, run in thread
+    const testsResult = await runTests(config, testFiles, []); //// async function, run in thread
+    exitCode = testsResult ? 0 : 3;
   }
   const time = (await new Date().getTime()) - startTime;
   await out(chalk.grey`\n${await time.toLocaleString()}ms\n`);
+  await process.exit(exitCode);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sxy-test-runner",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "license": "MIT",
   "homepage": "https://github.com/RobertSandiford/sxy-test-runner",
   "repository": {

package/readme.md

@@ -124,12 +124,6 @@ No option to re-run all tests on changes is currently available - I may add this
 
 Default behaviour is to re-run any failing test any time a change is made, even if that change isn't relevant to the failing test. This is to ensure you can see where attention is needed. Turn this off in the config if it is not convenient for you: config.watch.reRunFailingTests
 
-## Reloading modules
-
-A key challenge in creating an ESM test runner is re-loading modules due to the engine not letting us clear the import cache of ESM modules. This framework relies on sxy-loader, which uses a babel transform to transform modules into a reloadable format with a controllable cache. A cache of transformed code is kept to keep the process speedy.
-
-Performance is a little less than a native module import, but not so much as to be notable inconvenience. Re-running only test related to changes keep performance strong even in very large projects.
-
 # Advanced usage
 
 ## 1. Run tasks at startup - setup
@@ -201,6 +195,9 @@ describe('something', ({it, beforeEachTest, afterEachTest, afterDescribe}) => {
 
 ```
 
-# Known issues
+# Exit codes for `once`
 
-sxy-loader effectively uses eval to run modules, to get around the ESM limited of being unable to reload modules. This has a harmful effect on error reporting when code hits errors. I have some plans to work on error reporting, or work to get changes made to the ESM spec, but at current time error reporting isn't great.
+0: success
+3: some test errors
+2: other error
+It may also crash due to exceptions without giving any of these errors codes