See what colors look like in GitHub Actions

.github/workflows/check.yml

@@ -44,21 +44,9 @@ jobs:
         env:
           NO_ELM_TOOLING_INSTALL: 1
 
-      - name: elm-tooling install
-        run: npx --no-install elm-tooling install
+      - run: npx elm-tooling install
 
-      - name: Flow
-        run: npx --no-install flow check
+      - run: node print.js
 
-      - name: ESLint
-        run: npx --no-install eslint --report-unused-disable-directives .
-
-      - name: Prettier
-        run: npx --no-install prettier --check .
-
-      - name: elm-format
-        run: npx --no-install elm-format --validate elm
-
-      - name: elm-review
-        run: npx --no-install elm-review
-        working-directory: elm
+      - run: npx node ../bin/elm-test --color
+        working-directory: example-application

elm/src/Test/Reporter/Console.elm

@@ -210,10 +210,10 @@ reportSummary useColor { todos, passed, failed, duration } autoFail =
         headline =
             case headlineResult of
                 Ok str ->
-                    underline (green ("\n" ++ str ++ "\n\n"))
+                    (green ("\n" ++ str ++ "\n\n"))
 
                 Err ( colorize, str, suffix ) ->
-                    [ underline (colorize ("\n" ++ str))
+                    [ (colorize ("\n" ++ str))
                     , colorize (suffix ++ "\n\n")
                     ]
                         |> Text.concat

lib/Generate.js

@@ -274,6 +274,7 @@ function generateElmReportVariant(
       return 'JUnitReport';
     case 'console':
       if (supportsColor) {
+        console.log('ConsoleReport UseColor');
         return 'ConsoleReport UseColor';
       } else {
         return 'ConsoleReport Monochrome';

lib/Supervisor.js

@@ -54,6 +54,7 @@ function run(
               }
               break;
             case 'summary':
+              console.log(JSON.stringify(makeWindowsSafe(result.summary)));
               console.log(makeWindowsSafe(result.summary));
               break;
             default:
@@ -161,6 +162,7 @@ function run(
         }
 
         var response = JSON.parse(data);
+        console.log('READ', response);
 
         switch (response.type) {
           case 'FINISHED':

print.js

@@ -0,0 +1,7 @@
+console.log('\u001B[7mThis text is inverted\u001B[27m');
+console.log('\x1b[31mThis text is red\x1b[0m');
+console.log('\u001b[31mThis text is red\u001b[0m');
+console.log('\u001b[31m\nThis text is red\u001b[0m');
+console.log(
+  '\u001b[31mTEST RUN FAILED\u001b[39m\u001b[31m\n\n\u001b[39m\u001b[2mDuration: \u001b[22m154 ms\n\u001b[2mPassed:   \u001b[22m3\n\u001b[2mFailed:   \u001b[22m9\n\u001b[2mTodo:     \u001b[22m3\n\x1b[0m'
+);

templates/after.js

@@ -19,6 +19,7 @@ client.on('data', function (msg) {
 
 // Use ports for inter-process communication.
 app.ports.elmTestPort__send.subscribe(function (msg) {
+  console.log('MSG', msg);
   // We split incoming messages on the socket on newlines. The gist is that node
   // is rather unpredictable in whether or not a single `write` will result in a
   // single `on('data')` callback. Sometimes it does, sometimes multiple writes