#kotest — Public Fediverse posts

Kotlin devs and fans, here’s your top reading list 🔥
Check trending Kotlin articles from our blog - packed with practical insights, patterns, and tools:

1️⃣ https://softwaremill.com/7-kotlin-libraries-and-frameworks-for-backend-development-you-should-know/
2️⃣ https://softwaremill.com/handling-errors-in-kotlin/
3️⃣ https://softwaremill.com/kotest-the-kotlin-testing-framework-you-will-love/
4️⃣ https://softwaremill.com/kotest-the-kotlin-testing-framework-you-will-love/
5️⃣ https://softwaremill.com/meet-kotlin-2-1-from-non-local-exits-to-multi-dollar-strings/

✨ Whether you're leveling up your stack or diving into Kotlin’s new features, these pieces are worth your time!

#Kotlin #BackendDevelopment #Kotest #Ktor #Programming #DevReads

Kotlin devs and fans, here’s your top reading list 🔥
Check trending Kotlin articles from our blog - packed with practical insights, patterns, and tools:

1️⃣ https://softwaremill.com/7-kotlin-libraries-and-frameworks-for-backend-development-you-should-know/
2️⃣ https://softwaremill.com/handling-errors-in-kotlin/
3️⃣ https://softwaremill.com/kotest-the-kotlin-testing-framework-you-will-love/
4️⃣ https://softwaremill.com/kotest-the-kotlin-testing-framework-you-will-love/
5️⃣ https://softwaremill.com/meet-kotlin-2-1-from-non-local-exits-to-multi-dollar-strings/

✨ Whether you're leveling up your stack or diving into Kotlin’s new features, these pieces are worth your time!

#Kotlin #BackendDevelopment #Kotest #Ktor #Programming #DevReads

In #kotest tests are just functions. So they can be extracted into other extension functions like this:

fun FunSpec.someTests() {
test("1") {...}
test("2") {...}
}

Clever but the problem is that you can't run just one test from IDE 😒 Use abstract class instead? #UXfail

In #kotest tests are just functions. So they can be extracted into other extension functions like this:

fun FunSpec.someTests() {
test("1") {...}
test("2") {...}
}

Clever but the problem is that you can't run just one test from IDE 😒 Use abstract class instead? #UXfail

Back to #kotest rants. Because kotest has “built in coroutine support at every level” when an assertion fails, you can’t navigate to the matcher source code from the stack trace (Kotlin coroutines are stackless). So good luck if the error message is not very clear.

Back to #kotest rants. Because kotest has “built in coroutine support at every level” when an assertion fails, you can’t navigate to the matcher source code from the stack trace (Kotlin coroutines are stackless). So good luck if the error message is not very clear.

What about namespace "pollution" by extension functions in #Kotlin? E.g. a library with `fun Any?.print()` (yes, it's a #kotest #rant again) will add `print()` to code completion popup for all objects. Sure, IDE can deprioritise it, but maybe don't do it in the first place?

What about namespace "pollution" by extension functions in #Kotlin? E.g. a library with `fun Any?.print()` (yes, it's a #kotest #rant again) will add `print()` to code completion popup for all objects. Sure, IDE can deprioritise it, but maybe don't do it in the first place?

More #kotest #rants... shouldHaveSize() is helpful enough to print the whole (actual) list when sizes don't match. Good idea unless the list contains large data classes. Good luck scrolling around Gradle output for the failure message. OTOH it could be symptom of a bad test 🤔

More #kotest #rants... shouldHaveSize() is helpful enough to print the whole (actual) list when sizes don't match. Good idea unless the list contains large data classes. Good luck scrolling around Gradle output for the failure message. OTOH it could be symptom of a bad test 🤔

Another #kotest #rant is that most of its matchers don’t show diff window in IntelliJ with JUnit5 runner. It tries but most matchers throw AssertionError (no diff) and some AssertionFailedError (has diff) 🤷‍♂️😒 Makes you wonder if kotest authors actually use it via IntelliJ.

Another #kotest #rant is that most of its matchers don’t show diff window in IntelliJ with JUnit5 runner. It tries but most matchers throw AssertionError (no diff) and some AssertionFailedError (has diff) 🤷‍♂️😒 Makes you wonder if kotest authors actually use it via IntelliJ.

Kotest has eventually() function which retries lambda until it succeeds or times out. Not the best idea to use it across all tests in the first place, but in addition kotest prints stack trace from the first and the last failure, so you end up scrolling down 🤦‍ #kotest #rant

Kotest has eventually() function which retries lambda until it succeeds or times out. Not the best idea to use it across all tests in the first place, but in addition kotest prints stack trace from the first and the last failure, so you end up scrolling down 🤦‍ #kotest #rant

Are you ready for #Hacktoberfest!?

I've prepared my #JetBrains #Ktor #ArrowKt
example with #SqlDelight
#testcontainers and #kotest in #Kotlin with 19 issues for hacktoberfest!

I'll be giving personal guidance to everyone wanting to learn, and contribute.

https://github.com/nomisRev/ktor-arrow-example

Are you ready for #Hacktoberfest!?

I've prepared my #JetBrains #Ktor #ArrowKt
example with #SqlDelight
#testcontainers and #kotest in #Kotlin with 19 issues for hacktoberfest!

I'll be giving personal guidance to everyone wanting to learn, and contribute.

https://github.com/nomisRev/ktor-arrow-example