chore: log errors in acceptance tests (#5180)

When a Snyk CLI command is expected to exit 0 in acceptance tests, it
would be useful for debugging to see the stderr from the process.

This adds an option to runSnykCLI (logErrors) to do this, opt-in. That
way we don't pollute the log with expected non-zero exits in tests that
expect them.

test/jest/acceptance/cli-args.spec.ts

@@ -380,6 +380,7 @@ describe('cli args', () => {
       {
         env,
         cwd: project.path(),
+        logErrors: true,
       },
     );
 
@@ -401,6 +402,7 @@ describe('cli args', () => {
       {
         env,
         cwd: project.path(),
+        logErrors: true,
       },
     );
 
@@ -419,6 +421,7 @@ describe('cli args', () => {
       {
         env,
         cwd: project.path(),
+        logErrors: true,
       },
     );
 
@@ -436,6 +439,7 @@ describe('cli args', () => {
       {
         env,
         cwd: project.path(),
+        logErrors: true,
       },
     );
 
@@ -458,6 +462,7 @@ describe('cli args', () => {
         {
           env,
           cwd: project.path(),
+          logErrors: true,
         },
       );
       const jsonOutput = JSON.parse(stdout);

test/jest/util/runCommand.ts

@@ -11,7 +11,10 @@ type RunCommandResult = {
 
 // bufferOutput sets the RunCommandResult stdoutBuffer and stderrBuffer
 // useful if the stdout or stderr string output is too large for the v8 engine
-type RunCommandOptions = SpawnOptionsWithoutStdio & { bufferOutput?: boolean };
+type RunCommandOptions = SpawnOptionsWithoutStdio & {
+  bufferOutput?: boolean;
+  logErrors?: boolean;
+};
 
 const runCommand = (
   command: string,
@@ -50,6 +53,10 @@ const runCommand = (
         result.stderr = Buffer.concat(stderr).toString('utf-8');
       }
 
+      if (options?.logErrors && result.code !== 0) {
+        console.log('stderr:', result.stderr);
+      }
+
       resolve(result);
     });
   });