Detect test failures from test code?

[hurrymaplelad]

Is there a way to detect if any test has failed from within test code?

describe('some tests', function () {
  /*
   * Run some tests...
   */
})

after(function () {
  failures = ? // <--- what goes here?
  console.log(failures + " tests failed!")
})

I'd use this to keep chromedriver's browser open if a test failed, and to report success or failure to sauce labs after tests run. I could see pulling saucelabs reporting out into a reporter using multiple reporters #930, but keeping chromedriver open makes most sense in test code, where we launch the browser.

Runner and Reporters have the info I'm looking for as stats but I'm not sure how to get to them from within a test file.

[hurrymaplelad]

WD cleverly tracks each test's state in test land, and remembers if any failed. Trouble is, failures in before blocks won't hit the afterEach recording a failure, and will report pass to saucelabs...

[Whoaa512]

Also ran into this problem while creating an afterEach to take screenshots of failed tests. I think I have a decent workaround in this commit

[EndangeredMassa]

Failures in before will still call after, but not afterEach. I could really benefit from having it still call afterEach in this case.

Was this specific case intended by the symmetrical hooks change? #1043

[travisjeffery]

there's no good way to do it within a test. but it could/should be done in a reporter.

@EndangeredMassa that's how it was written, if before fails then it doesn't make sense to run beforeEach and then it doesn't make sense to run afterEach imo.

i'm gonna close this. the multiple reporters way would be best.