thanks! - Ill give that a go - appreciate the resp...

# arrow

[Carter Youngblood]

thanks! - Ill give that a go - appreciate the response - love Arrow btw 🙂

[Mike]

Try moving to Kotest 4 (Kotlintest's new name). It's in BETA1. Solid, and upgraded Arrow assertions.

https://github.com/kotest/kotest/tree/4e3b138efe3275e671c4ae88350d1ed2d06dadd0

[Carter Youngblood]

👍 - I will go that route first, before I worry about transitive dependencies 🙂

[Kristian]

I had the same issue, cause by kotlintest. Fixed it with an exclude in gradle.

testImplementation("io.kotlintest", "kotlintest-runner-junit5", kotlinTestVersion) {
    exclude("io.arrow-kt")
}
testImplementation("io.kotlintest", "kotlintest-assertions-ktor", kotlinTestAssertionsVersion) {
    exclude("io.arrow-kt")
}
testImplementation("io.kotlintest", "kotlintest-assertions-arrow", kotlinTestAssertionsVersion) {
    exclude("io.arrow-kt")
}

[simon.vergauwen]

@Mike exciting to see! I’ll slide into the #kotest channel for some question about the beta 😁

[Mike]

I was excluding Arrow dependency, too and created my own copies of matchers for some arrow features.

Upgraded yesterday. I think the change is more about package renames, with some new functionality. Migration not too bad as a lot still exists under old package to ease migration.

[simon.vergauwen]

Awesome, I’m interested mostly in the non-blocking support we’ll get. So I can more precisely follow my tests, not the whole suite hangs if a single test hangs. Quite annoying to figure out which tests are misbehaving etc.

[simon.vergauwen]

Especially when dealing with concurrency, cancellation and parallelism 😄