Unit tests for haveFailed() matcher are incomplete

[modocache]

Tests should be added for the cases in which the result is a failure, but doesn't match the specified domain or description.

[m3ta4a]

I've submitted a PR that breaks a couple haveFailed() specs (but updates to latest Nimble), once I figure out how to fix them I'll try to add the requested tests. Help would be appreciated though, I'm lacking context and intent. @modocache

[m3ta4a]

It looks like version 7.0.0 of Nimble introduced a change which evaluates the expressions in a try clause for the purpose of clarifying failure messages (line 48 in Nimble's Expectation.swift). This breaks the haveFailed() specs which intentionally throw errors, since Nimble catches them. It might be prudent to add new matchers which expect errors to be thrown, as opposed to expecting a failure?

[m3ta4a]

🦗🦗🦗🦗🦗🦗🦗 ... anyone here?