disabling detailed_output hides failure reasons and ignores skip_testcases_on_fail setting

[HugoMuller]

Hi,
I'm using nightwatch v0.9.8, with this piece of config:

{
  // ...
  "test_workers": {
    "enabled": true,
    "workers": "auto"
  },

  "live_output": true,
  "detailed_output": false,

  "test_settings" : {
    "default" : {
     // ...
      "desiredCapabilities": {
        "browserName": "chrome",
        "javascriptEnabled": true,
        "acceptSslCerts": true
      },
      "skip_testcases_on_fail": false
    }
  }
}

As expected, there is no assertion output. The doc says for detailed_output setting:

Set this to false if you'd like to only see the test case name displayed and pass/fail status. This is especially useful when running tests in parallel.

So when a test fails, I don't know why because the reason is swallowed. That's not very helpful.
Second problem, in case of failure, nightwatch doesn't continue the current test suite and execute the next one. This happens only with detailed_output = false.
I can't reproduce with detailed_output = true: nightwatch continue the suite after a failure.

Am I doing it wrong? Or is detailed_output buggy?

[beatfactor]

It could be a bug, it's a relatively new feature. Can you also disable "live_output" and see if it makes any difference?

[HugoMuller]

When I disable live_output, there is no log about the test suite containing the failure. The suite is ignored in the report, as if the buffer is cleared in case of failure, or something.
Actually, it seems that the error raised by the failing assertion is not catched by nightwatch when detailed_output is disabled.

[beatfactor]

Yeah, it's broken alright. A fix will be posted soon, thanks for bringing it up.