Hi there, I just noticed that

io.kotest.core.datatest.NamesKt#isStable(kotlin.reflect.KType)

return false, when the parameter is enum class. Is it expected?

I have a super weird case, somewhat related to Kotest but I’m not sure really. Let’s say I have a class

Foo

and a factory which always returns the same value as long as the previous one is still referenced:

class Foo

class FooFactory {

    var fooRef: WeakReference<Foo>? = null
    
    fun get() = fooRef?.get() ?: Foo().also { fooRef = WeakReference(it) }
}

So far so good. Now I have spec which should assert that the objects are in memory as expected. This overall might be tricky because GC is not very deterministic, but it’s stable enough:

class TestSpec : DescribeSpec() {

    private val fooFactory = FooFactory()

    init {
        describe("foo") {
            var foo: Foo? = fooFactory.get()
            // println(foo)

            describe("bar") {
                gc()
                fooFactory.fooRef?.get() shouldNot beNull()

                foo = null
                gc()
                fooFactory.fooRef?.get() should beNull()

                it("should do something") {
                    println("Done")
                }
            }
        }
    }

    override fun isolationMode() = IsolationMode.InstancePerLeaf
}

And now the tricky part: if the

println(foo)

is commented out, the test works. But if it’s not, then the test fails at the

should beNull()

line. Apparently something is holding it. I checked in IJ’s memory tool and it looks like it’s just a variable being kept, but I have no clue why and how this would happen. Also I expect that with

InstancePerLeaf

this entire thing is executed just once anyway, as there’s only one leaf. Any ideas?

Hi guys, with the release of 1.4.30 are you any closer of supporting js ir?

Have there been any changes to exceptions matchers in 4.4.0? Some of our tests started failing and it turns out previously the exceptions that we compared didn’t have matching

cause

. Is there an issue I can read to see what’s changed exactly?

Would appreciate any feedback on https://github.com/kotest/kotest/issues/2065

Hey!. I'm facing an issue while trying to work on https://github.com/kotest/kotest/issues/2011 and honestly I thought someone here would be able to help. 😅 When opening

kotest

in Intellij, and adding a new module under

kotest-extensions

(e.g.

io.kotest.extensions.htmlreporter

), I can't for the life of me find a way to import

io.kotest.core

. I'm sure this is probably something obvious that I'm missing but I've tried a couple different ways and can't seem to understand what...if anyone has any idea, I'd be extremely thankful. You can see the code (2 files) I added here:https://github.com/caramelomartins/kotest/tree/master/kotest-extensions/kotest-extensions-htmlreporter. Thanks!

Does KoTest has support for virtual time in tests ? I'm testing a component that uses

delay

and I'd like to check that at least X seconds has elapsed between 2 operations.

TestCoroutineDispatcher

from

kotlinx-coroutines-test

has this capability but I can't find a way to use it with

StringSpec

.

why does this not work the way I would expect?

for the first, the tests aren't nested and so when they start to repeat through the inner loop on the second outer loop, I get 'duplicate' test name errors. but if I create that test internally, now there are two tests with that name. Here is a demonstration of the issue by just adding a prefix to the test

@sam do you still recall our convo about edgecases missing when there's one arb with empty edgecases? i'd be inclined to look into fixing that in the next few days. would this be the right time for me to start looking at it or do i wait until 4.5?

qq is there a way to rerun build on a pr branch?

Hi! If I need to configure an instance of a testcontainer for postgres, where whould I do that? It seems like

Startable.perProject(...)

takes a name param, but doesn't work for a customized container...

Also, do listeners get run in the order they are declared? (I need to get the db running before Micronaut's extension starts up...)

Hi.. I keep getting this error after I updated to Kotlin 1.4.30, while trying to use this dependency

io.kotest:kotest-assertions-core:

in commonTest:

Compilation failed: Backend Internal error: Exception during IR lowering
File being compiled: /Users/runner/work/kotest/kotest/kotest-assertions/kotest-assertions-core/src/commonMain/kotlin/io/kotest/matchers/collections/decreasing.kt
The root cause java.lang.AssertionError was thrown at: org.jetbrains.kotlin.ir.overrides.FakeOverrideBuilderStrategy.fakeOverrideMember(IrOverridingUtil.kt:43)

 * Source files: 
 * Compiler version info: Konan: 1.4.30 / Kotlin: 1.4.30
 * Output kind: STATIC_CACHE

I'm getting a very puzzling problem... even though I added the Micronaut extension, it seems like it's just being ignored...

~~~ Kotest Configuration ~~~
...
-> Extensions
  - io.micronaut.test.extensions.kotest.MicronautKotestExtension
  - io.kotest.engine.extensions.SystemPropertyTagExtension
  - io.kotest.core.extensions.RuntimeTagExtension
  - io.kotest.engine.extensions.RuntimeTagExpressionExtension
-> Listeners
  - io.micronaut.test.extensions.kotest.MicronautKotestExtension
  - beforeAfterAllListener$1

Just out of curiosity - how painful is it keeping the plugin working with each new IntelliJ version? Are we talking minutes, hours, days or weeks to get a version out that supports an EAP?

Am I missing a trick to test Ktor (clients)? I'm using

MockEngine

(from ktor) in a

FunSpec

, and the code is definitely being run (I see the failure message being logged) but the actual test passes

Hi! Why are versions of "kotest-core-jvm" lagging behind "kotest-assertions-core-jvm" etc?

Is kotest available for native targets yet?

Hello, I have just started using kotest, and I have noticed that it’s not possible to run all test in one time, the kotest plugin show only tests available in the selected class, and when I tried to run all tests through the test folder as with junit I got this message “No tests found for given includes”, how can I fix that ?

I think we should revisit this as a topic of discussion - At the moment, this would be a blocker to upgrading my kotest version, but more importantly its a bit of a blocker to properly setting up edgecases - theres an incentive to just ignore them so that our tests don't balloon out into the hundreds of thousands of iterations. What do you think @sam and @mitch?

Hello, Does anyone have a very minimal build.gradle.kts file for running kotest on multiplatform jvm/js? I tried following the get started guide but the js dependency cannot be resolved by gradle.

implementation 'io.kotest:kotest-framework-engine:$version'

hi @sam - have you seen this with coroutines 1.4.3 (released this morning):

java.lang.NoSuchMethodError: 'java.lang.Object kotlinx.coroutines.DelayKt.delay-p9JZ4hM(double, kotlin.coroutines.Continuation)'
	at io.kotest.assertions.timing.EventuallyKt.eventually(eventually.kt:118)
	at io.kotest.assertions.timing.EventuallyKt$eventually$10.invokeSuspend(eventually.kt)

@sam By updating to kotlin 1.4.30 and using the

watchos

shortcut, you have effectively removed watchosx86. Can you remove the shortcut and add the separate watchos targets manually?

having a little trouble getting tests to run in sub sub project, eg: https://docs.gradle.org/current/userguide/intro_multi_project_builds.html#sec:multiproject_build_and_test … it would be

:services:shared:test

I’ve got a test structured something like:

context("when starting a Foo") {
    context("and thing A happens") {
        should("throw an error") {
        }
    }
    context("and thing B happens") {
        should("throw an error") {
        }
    }
}

and when I get a failure, in the junit output I just get:

"should throw an error"

for context, which is ambiguous between those 2 cases. Is there a way to get the full context “tree” when a failure happens?

test is simple

class MathKtTest : FreeSpec({
    data class Points(
        val apr: String,
        val term: Int
    )
    "calculate discount factor" - { 
        forAll(
            row("1", 12)
        ) { (apr, term) ->
            val D = calculateDiscountFactor(BigDecimal(apr), term)
            assertEquals(BigDecimal("75.6813"), D)
        }
    }
})

method is a top level method

fun calculateDiscountFactor(apr: BigDecimal, term: Int) :BigDecimal{
    val r = apr
    val n = 12 * term
    val denominator = { ((BigDecimal.ONE + apr).pow(n)) - BigDecimal.ONE }
    val numerator = { r * (BigDecimal.ONE + r).pow(n) }
    return numerator() / denominator()
}

kotest version 4.4.1, plugin version

1.1.30-IC-2020.3

kotlin version 1.3.72

Is there a way to only enable a project extension if actually needed in one of the test classes being run? I need some testcontainers to come up but only for certain tests, and stay alive for other classes that might need them.

Hi It seems

kotest-extensions-robolectric

didn’t release with the latest version

4.4.x

but stay at

4.3.2

. Is there any plan to bump it to the latest version? https://mvnrepository.com/artifact/io.kotest/kotest-extensions-robolectric-jvm

@sam qq relaying a q from a colleague. do you have a suggestion on how can we register listeners to say checkAll per scope e.g. nested in a context? Right now we've been using explicit function calls / passing various explicit proptestconfig that carries a listener with it. Curious if you have a better idea around that