Is a

suspend

version of

shouldThrow

missing for a reason or should I file an issue?

@sam I've raised an issue on Quarkus repo about getting Kotest properly integrated. I also filed a PR to update the Quarkus example to latest deps, just as housekeeping 👍 One of the Quarkus devs who is more familiar with/has worked on the JUnit integration commented on the repo after pulling the broken example. Whenever you're not in 🌴 mode, do you think you'd be able to join in on the conversation here? Would be appreciated -- I'm not an expert in either Kotest, JUnit, or Quarkus unfortunately 😅 https://github.com/quarkusio/quarkus/issues/19749

Until 5.0 there not will be the new targets no? Is there a date for it?

If so, it's coming in 5.0 - currently you can use it in snapshot mode

This currently fails, since Kotest is not comparing literals. Would it make sense to raise an issue on this?

test("comparing doubles") {
         "3.123456789123457" shouldNotEqualJson "3.123456789123456789123456789"
      }

If anyone wants to try MPP support https://kotest.io/docs/framework/multiplatform.html

@sam i’ve got a proposition for you. It’s about introducting continuation-passing style to the current arbitrary builder to improve its ergonomics and simplify how we might build, compose, and generate arbs. I’ve got a PR up for you to hopefully illustrate the proposed solution as well as the problem that solves. Hope you can take a bit of a peek when you’ve got the time https://github.com/kotest/kotest/issues/2493

Hello not sure if i should ask in here or in the testcontainers slack so apologies if this is in the wrong place. i'm using tests containers + kotest for integration tests (mongo + kafka containers). I'm finding that the first integration test passes, but subsequent tests are failing because the host machine ports are now unavailable. Everything works in isolation, its only when all my integration tests are run that the issue pops up. I've tried putting in a short delay after the containers are told to stop but it doesn't seem to work. Any suggestions?

Hello, Is there support for returning a value from the new eventually API’s? I’m looking at https://kotest.io/docs/framework/concurrency/eventually.html for details. I currently have something like this with kotest in 4.4:

suspend fun RecommendationsExhaustedEventRepository.findByCausationIdEventually(causationId: UUID): RecommendationsExhaustedEvent {
    return eventually(30.seconds, IllegalStateException::class) {
        checkNotNull(
            this.findByCausationId(causationId)
        )
    }
}

and trying to do the same thing with 4.6. FWIW, I’m also fine with leaving the eventually as is, and not moving to the new API, but I get this too:

java.lang.NoSuchMethodError: 'java.lang.Object io.kotest.assertions.timing.EventuallyKt.eventually-8-LJAvk(double, kotlin.reflect.KClass, kotlin.jvm.functions.Function1, kotlin.coroutines.Continuation)'

I see that error with Kotlin 1.4.32 and 1.5.30

I've just added a

config=

to

checkAll

with two gen-arguments and it started to throw StackOverflowException. I checked in sources and it looks like it does indeed recursively calling itself: source on github Shouldn't it call

proptest

instead?

Trying to debug a test inside of a

ShouldSpec

should

block. Test looks something like this:

class MyTest : ShouldSpec({
  val foo = "bar"

  should("do something") {
     true shouldBe true // place breakpoint here
  }
})

If I run the test using the Kotest plugin in debug mode and place a breakpoint at the

true shouldBe true

line I don’t see the

foo

variable captured in the “Variables” window like I would expect. I recall being able to debug this relatively recently so I think this is a new issue. Kotlin version — 1.5.30 IntelliJ version — IntelliJ IDEA 2021.2.2 (Ultimate Edition) Build #IU-212.5284.40 Kotest version — 4.6.1 Kotest plugin version — 1.1.36-IC-2021.1 * Not a contribution *

where can I find the kotest 4.6.3 changelog?

Any way to get more information out of kotest? I have a test run that gets through 3 tests successfully and then just hangs (using gradle or kotest plugin).

Hi Is there a way to assert a function is invoke a X number of times ? (X can be zero ) - could not find it in the kotest docs ( also I don’t see a search text field in the docs..) Thanks

Anyone know where the https://kotest.io/docs/extensions/junit_xml.html reporter is? I can't find the gradle coordinate

Hello All, @sam has anyone came across the issue after upgrade of gradle version to 7.2 to add support for android jetpack compose. The test cases do pass but the build fails with an exception

Received a completed event for test with unknown id '8.4'. Registered test ids: '[8.1, :app:testDebugUnitTest, 8.2]'

Here are my gradle settings

------------------------------------------------------------
Gradle 7.2
------------------------------------------------------------

Build time:   2021-08-17 09:59:03 UTC
Revision:     a773786b58bb28710e3dc96c4d1a7063628952ad

Kotlin:       1.5.21
Groovy:       3.0.8
Ant:          Apache Ant(TM) version 1.10.9 compiled on September 27 2020
JVM:          11.0.8 (JetBrains s.r.o 11.0.8+10-b944.6916264)
OS:           Mac OS X 10.16 x86_64

Guys any help would be appreciated or i have to rewrite all my existing unit tests in the project using junit5 or junit4. I have also added a detailed explanation https://github.com/kotest/kotest/issues/2331#issuecomment-923422181

Hello everyone! I have the following data structure:

data class User(
    val id: String,
    val someTime: LocalDateTime,
    val someDetails: SomeDetails,
) {
    data class SomeDetails(
        val otherId: String,
        val otherTime: LocalDateTime,
    )
}

val user = User(
    id = "1",
    someTime = LocalDateTime.now(),
    someDetails = User.SomeDetails(
        otherId = "a",
        otherTime = LocalDateTime.now().plusSeconds(1)
    )
)
val otherUser = User(
    id = "1",
    someTime = LocalDateTime.now().plusHours(1),
    someDetails = User.SomeDetails(
        otherId = "a",
        otherTime = LocalDateTime.now().plusSeconds(22)
    )
)

I would like to write a test that ignores both

LocalDateTime

fields. Something in the lines of:

class SomeTest {
    @Test
    fun `should ignore localdatetime fields`() {
        user.shouldBeEqualToIgnoringFields(otherUser, User::someTime, User.SomeDetails::otherTime)
    }
}

Is there any matcher that I might have missed when going through the docs? Thanks in advance!

Hello all!! is it possible to configure kotest to use TestCoroutineScope instead of normal coroutines? https://stackoverflow.com/questions/69417255/kotest-and-kotlinx-coroutines-test-integration

I am currently using Eventually but still with that, there are times when test fails, the Code under test schedule some task on a separate thread pool, which is supposed to completed with 2-3 seconds yet depending upon the load on CI agent where these test are running they can take say 7-8 second to complete resulting in test failure, one option is to increase timeout duration in eventually above 8 second, but depending upon the number of such test this will increase the overall build time.

Hi developers. I have a test with 2 `Arb`s and would like to filter the second based on the first value. The best I could think of was this

Arb.pair(ArbA, ArbB).filter {it.first != it.second}

But then the result is a pair that I need to unpack for the test. Is there a better way?

Hi, after updating my Kotlin and Kotest versions in IntelliJ I’m getting the below warning where I’m using

.config

to tag my tests, for example:

"my test".config(tags = setOf(TestTag)) {
    // Test stuff here
}

warning on .config -

This declaration is experimental due to signature types and its usage must be marked (will become an error in 1.6) with '@kotlin.time.ExperimentalTime' or '@OptIn(kotlin.time.ExperimentalTime::class)'

TestTag would be defined like this -

object TestTag : Tag()

Is there something else I should be doing to tag my tests instead of using

.config

?

Is there any M1 or M2 release planned for https://github.com/kotest/kotest-extensions-arrow ? is that namespace correct? should that be under

kotest.extensions.arrow.*

?

I'm bumping up some lib with the latest(sh) kotest

api("io.kotest:kotest-runner-junit5:4.6.1")
api("io.kotest:kotest-assertions-core:4.6.1")

this used to work in the past, but now it doesnt get picked up any more

init {
        val BCN_Epileptic = "BCN_Epileptic.X"
        BCN_Epileptic {
            ...
        }
    }

It works only if I use instantiate and

invoke

on the string itself directly, that is

init {
        "BCN_Epileptic.X" {
            ...
        }
    }

Is it possible to pass two dir files and assert all files and directories have the same structure and content?

According to this documentation, An innermost test in FreeSpec must not use ‘-’(minus sign). But the innermost test with the minus sign works well 🤔 What’s supposed to be wrong with it??

Is Gradle test filtering supported with Kotlin/Native? I’ve tried

./gradlew macosX64Test --tests '*MyTestClass'

and

./gradlew macosX64Test --tests 'MyTestClass'

but in both cases all tests still ran

Is it possible to compare function types? Given something like:

typealias Matcher = (String) -> Boolean
data class Thing(matcher: Matcher)

This fails:

it("compares values of function types") {
    val testThing = Thing({ it.startsWith("test") })
    testThing.matcher shouldBe { it.startsWith("test") }
}

with messages like:

expected:<(kotlin.String) -> kotlin.Boolean> but was:<(kotlin.String) -> kotlin.Boolean>

Is there a way to group assertSoftly into one matcher that can be reused ?

assertSoftly(foo) {
    shouldNotEndWith("b")
    length shouldBe 3
}
->
foo shouldBe customAssert

Hi folks 🙂 I stumbled upon an issue with the

JUnitXmlReporter

in one of my projects. I set it up according to the documentation, but the final XML files still only contain the leaf name of the tests for nested tests. What I have seen while debugging that the reporter itself is working correctly and directly after doing the file operations in the reporter the XML files are correct. But something happens afterwards overwriting the XML files from the

JUnitXmlReporter

😞 Anyone got an idea or can see the same behaviour? Im using version

4.6.3

of KoTest.