Support tests expecting Exceptions about specnaz HOT 2 CLOSED

The reason I'm not in love with this feature is that I never liked the JUnit's expect attribute. In my opinion, the tests are less readable with it, and a lot more fragile (I've often seen tests that passed, but the actual Exception was not thrown from the line that the author intended, and so they were in fact 'false positives').

As long as Specnaz doesn't have this feature, it forces people to look for alternatives - which is great, because a lot of alternatives exist, and they are all better than JUnit's expect:

• If you're using AssertJ for assertions, you have the assertThatThrownBy method for that exact scenario.
• There is the CatchException library, tailor-built for this purpose.
• Probably many others that I'm forgetting right now.

Design-wise, I don't see a problem with this feature. I would probably make the API look something like:

it.shoudThrow(IllegalArgumentException.class, "when called with a null argument", () -> {
    // the test name will be: "should throw IllegalArgumentException when called with a null argument"
    // ...
});

The perfect API would probably be:

it.shouldThrow<IllegalArgumentException>("when called with a null argument", () -> {
    // ...
});

..but I'm not sure that's possible with Java. I do know that KotlinTest does something like this, so perhaps that will be the API in the Kotlin version.

The only question is: do we want to do this, or do we rather skip this, forcing people to look for (better) alternatives?

from specnaz.

Fixed in 1.1 - resolving.

from specnaz.