That yields the following solution the the example above ``` fun doSomething() = IllegalAccessExc...

# arrow

[Shalom Halbert]

That yields the following solution the the example above

fun doSomething() = IllegalAccessException("message").left()

    @Test
    fun sample() {
        doSomething().shouldBeLeftThrowableWithMessage<IllegalAccessException>("message")
    }

[simon.vergauwen]

You can also compose Kotest asserstions.

[simon.vergauwen]

doSomething().shouldBeLeft().message shouldBe "message"

[simon.vergauwen]

shouldBeLeft uses smart-casting, and extracts the value out of Either after the assertions succeeds

[simon.vergauwen]

So you have access to Throwable after shouldBeLeft()

[Shalom Halbert]

Based on the documentation, it seems like the intended way to make assertion on a Left<Throwable> is by using

doSomething().shouldBeLeftOfType<IllegalAccessException>().message shouldBe "message"

[simon.vergauwen]

Oh, didn’t know that one. Guess I’m still holding on to some of my old assertions-core habits from before this lib 😅

[Shalom Halbert]

Hehe

[Shalom Halbert]

Well, it seems like that assertion is documented on Kotest’s website, but it’s not in the source code 😅

[simon.vergauwen]

Oh, I think that’s because it was deprecated in favor of composing existing assertions.

doSomething().shouldBeLeft().message shouldBe "message" or
doSomething().shouldBeLeft().shouldBeOfType<IllegalAccessException>().message shouldBe "message"

[simon.vergauwen]

Oh, that first one was broken. So yes, that has to be fixed in order for this change to makes sense IMO

[Shalom Halbert]

Ends up I simply messed up by using the wrong version (1.0.1 instead of 1.1.1) 🤦

[sam]

There's lots of improvements going into these extensions courtesy of @Imran/Malic

[Imran/Malic]

Hope to start updating the docs @Shalom Halbert soon after 1.2.0 is published I was stuck on a compiler error from 1.5.30

[Imran/Malic]

Here is a small correction on the docs https://github.com/kotest/kotest/pull/2685

[sam]

Merged