chore: disable "exit: true" in unit test config; force color
`exit: true` is only necessary in mocha if your code doesn't clean up after itself.  this is not needed for the unit tests--haven't tested with e2e tests yet
MODIFY
packages/gulp-plugins/lib/tasks/e2e-test.js
packages/gulp-plugins/lib/tasks/e2e-test.js
@@ -19,6 +19,7 @@ const configure = function configure (gulp, opts, env) {
timeout: opts.testTimeout,
'require': opts.testRequire || [],
exit: true,
+ color: true,
traceWarnings: opts.e2eTest.traceWarnings,
traceDeprecation: opts.e2eTest.traceWarnings,
};

MODIFY
packages/gulp-plugins/lib/tasks/unit-test.js
packages/gulp-plugins/lib/tasks/unit-test.js
@@ -12,9 +12,9 @@ const configure = function configure (gulp, opts, env) {
const mochaOpts = {
reporter: utils.getTestReporter(opts),
timeout: opts.testTimeout,
- exit: true,
traceWarnings: opts.test.traceWarnings,
traceDeprecation: opts.test.traceWarnings,
+ color: true
};
// set env so our code knows when it's being run in a test env
process.env._TESTING = 1;

chore: disable "exit: true" in unit test config; force color

`exit: true` is only necessary in mocha if your code doesn't clean up after itself.  this is not needed for the unit tests--haven't tested with e2e tests yet