Unit tests produce errors and warnings but do not fail

[faboweb]

Warnings and errors should produce an exit code 1 to show the tests have failed.

[NodeGuy]

Can you provide any examples?

[faboweb]

i.e.

 PASS  test/unit/specs/store/store.spec.js
  ● Console

    console.error app/src/renderer/vuex/store.js:87
      Encrypting the state failed, removing cached state.

     [vue-router] missing param for named route "validator": Expected "validator" to be defined
    console.warn node_modules/vue-router/dist/vue-router.common.js:18

[NodeGuy]

Your first example (Encrypting the state failed, removing cached state.) is a result of expected behavior from a passing test. The test is deliberately provoking the error message.

[faboweb]

Shouldn't then the console.error function be mocked out?

[NodeGuy]

That would be one way to approach it, yes. I think a better design would be to throw an exception and let higher-level code decide how to report it.

[faboweb]

Also a good strategy.