It seems like the Kotest intellij plugin's test browser ignores the context blocks in DescribeSpec...

Thanks for the plugin fix! Just wondering if there's any way the test browser could also work for test factories? (I have a separate file I declare the function I use to import into integration/unit test modules... that function doesn't seem to have such a view)

The plugin was updated today to 1.1.34-IC-202, kotest_version=4.4.3

Hi, I'm having a problem with

kotest

and

Android Studio

in a Kotlin multiplatform project. After adding the

kotest

dependencies to

build.gradle.kts

and reloading the project I get the following warning (not even an error):

Warning:<i><b>project ':partnerSDK': Unable to build Kotlin project configuration</b>
Details: org.gradle.internal.resolve.ArtifactNotFoundException: Could not find kotest-runner-junit5-4.4.3-samplessources.jar (io.kotest:kotest-runner-junit5:4.4.3).
Searched in the following locations:
    <https://repo.maven.apache.org/maven2/io/kotest/kotest-runner-junit5/4.4.3/kotest-runner-junit5-4.4.3-samplessources.jar></i>

This seems to cause

Android Studio

to stop working, and I'm no longer able to use code completion, or even run unit tests. This makes test creation extremely painful. If I manually create a test I'm able to run it using

./gradlew test

, so this is clearly not a problem with my configuration or Gradle... Has anybody faced this problem? Do you know how to solve it?

Maybe some sort of extension function

Is it possible to use

kotest

in a Kotlin Multiplatform Mobile project? I have included the following dependencies in the shared project:

val kotestVersion = "4.4.0"
kotlin {
    sourceSets {
        val commonTest by getting {
            dependencies {
                implementation("io.kotest:kotest-runner-junit5:$kotestVersion")
                implementation("io.kotest:kotest-assertions-core:$kotestVersion")
                implementation("io.kotest:kotest-property:$kotestVersion")
            }
        }
    }
}

but this fails when trying to build the project because there is no

ios_x64

variant of

kotest-runner-junit5

. Android Studio fails while reloading the project trying to find

kotest-runner-junit5-4.4.0-samplessources.jar

and

./gradlew build

explicitly fails due to the missing

ios_x64

variant not found.

Hello all! Could you let me a bit more details about running kotest in multiplatform project (JVM + JS)? According documentation I added into build.gradle.kts:

val commonTest by getting {
            dependencies {
                implementation(kotlin("test-common"))
                implementation(kotlin("test-annotations-common"))
                implementation("io.kotest:kotest-framework-engine:$kotestVersion") //<< This dependency
            }
        }

And wrote test:

class OperationResultSerializationTest: FunSpec({

    val json = Json {
        serializersModule = SerializersModule {
            polymorphic(Any::class) {
                subclass(TestPayload::class)
            }
        }
    }

    test("success action result should be serialized and deserialized") {
        val actionSuccessJson = json.encodeToString<ActionResult>(ActionSuccess)
        val actionSuccessDeserialized = json.decodeFromString<ActionResult>(actionSuccessJson)

        actionSuccessDeserialized shouldBe null //<<Should FAIL here (intentionally)
    }
})

But when I run it using gradlew check I get in IDEA just row:

Kotest 4.5 has been released. Feel free to share. https://kotest.io/docs/changelog.html

Why doesn't kotest support other K/N platforms like

linuxArm32Hfp

,

linuxMips32

,

mingwX86

? Is it due to kx.coroutines does not support it? 👀

is there a reason why

kotest-extensions-spring

is not released with 4.5.0 in maven-central? https://mvnrepository.com/artifact/io.kotest/kotest-extensions-spring I ran into the problem as I have a group-wide versioning and

kotest-extensions-spring

cannot be found in 4.5.0 😅 Is that a separately released lib?

I’m wondering why I don’t see compilation errors for assertions where types don’t match, for example

5 shouldBe "5"

. There’s no error shown, even though the signature would force the right-hand parameter to be a assignable to the left-hand one (

infix fun <T, U : T> T.shouldBe(expected: U?)

), or so I thought. Is this expected? It’s pretty annoying when refactoring code, because tests still compile but fail in runtime

Hello all. I updated to the latest version of kotest (4.5) and kotlin (1.5) and am seeing the following:

Runtime JAR files in the classpath should have the same version. These files were found in the classpath:
    /Users/jameseschner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk8/1.5.0/65fbc439df2e4aad1f3769762d54534f1b564090/kotlin-stdlib-jdk8-1.5.0.jar (version 1.5)
    /Users/jameseschner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk7/1.5.0/f61904618ea7be07a66e0545ffe8dc2c70a19b77/kotlin-stdlib-jdk7-1.5.0.jar (version 1.5)
    /Users/jameseschner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.5.0/29dae2501ca094416d15af0e21470cb634780444/kotlin-stdlib-1.5.0.jar (version 1.5)
    /Users/jameseschner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.5.0/4080d69efca5e39e9b4972f125e40f1607bd6460/kotlin-stdlib-common-1.5.0.jar (version 1.5)
    /Users/jameseschner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-script-runtime/1.4.31/183616b52cfb8ddaa8a2a15bf926e87dfcddcde3/kotlin-script-runtime-1.4.31.jar (version 1.4)

Looks like kotest is pulling in 1.4.31:

+--- io.kotest:kotest-runner-junit5 -> 4.5.0
|         +--- io.kotest:kotest-framework-engine:4.5.0
|         |    \--- io.kotest:kotest-framework-engine-jvm:4.5.0
|         |         +--- org.jetbrains.kotlin:kotlin-script-runtime:1.4.31

Is kotest planning on moving to 1.5 soon? * Not a Contribution *

Is it intentional that when using

it("some test description")

without the trailing lambda, the test should pass? Why should that behaviour be needed? I would have thought that at least for TDD -- it should fail... I use this form just to outline the tests I need to write, but one might easily forget to implement them if they pass...

Also, funny that ignored tests don't appear in IDEA U....

Is there any way to run the tests such that new spec instance is created for every container that contains tests, but all the tests inside are executed on that one instance? My motivation is that the assertions shouldn’t do any side effects, and so it’s a bit wasteful to repeat the entire setup for each test. So, I’d like this:

DescribeSpec({
  describe("a") {
    println("a")

    describe("b") {
      println("b")

      it("check 1") { println("1") }
      it("check 2") { println("2") }
    }

    describe("c") {
      println("c")

      it("check 1") { println("1") }
      it("check 2") { println("2") }
    }
  }
})

to print

a // first instance
b
1
2
a // second instance
c
1
2

Starting a thread about memory usage since the previous one is long enough 🙂

Another one 😄 https://github.com/kotest/kotest/commit/a0ea126434401074dc8d1839fb986c23a74780c1 this commit didn’t really change anything because I was running tests with Gradle, and this discovery path is not even hit — Gradle (Junit?) passes all requested tests classes already, Kotest just filters them to keep Spec instances. The 4GB of memory that ClassGraph takes is triggered by

detectConfig()

. Disabling jar scanning for it is not reasonable, because jars may provide listeners. So while config discovery is pretty useful, would you consider some other mechanism for that? I know that scanning can be disabled, but then modules wouldn’t be able to provide useful listeners (I think I even requested discovery at one point, to avoid having to declare a merged project config in each module). One thing that comes to mind is allowing everything that can be AutoScanned now to be provided via ServiceLoaders. Locally I just hardcoded our listeners and got that peak memory down from 4GB to 1GB. Bottom line: ClassGraph has significant memory impact, at least with larger projects. It’d be nice to have a way to completely bypass it. Btw in addition to memory usage, it also spawns several threads (in my case 18!) that it never releases.

Are there any future plans to extend

io.kotest:kotest-property

with stateful testing? 🙂

the docs for stringspec state that it does not support nested tests. is that still true?. https://github.com/kotest/kotest/blob/master/doc/styles.md#string-spec

What's the best way to generate a base64 token with Arb?

Should I make an Arb for each one using a function that takes the

entity1Id

as a parameter, or is there a better way?

How can I ensure that

Arb.set

or

Arb.list

generates unique entries by my entity id?

Has anyone faced this error with latest Kotest: 4.6.0 with Gradle 7.0, gradle-jvm:16, Kotlin: 1.6, Java: 16

Supertypes of the following classes cannot be resolved. Please make sure you have the required dependencies in the classpath:
    class io.kotest.core.test.TestContext, unresolved supertypes: kotlinx.coroutines.CoroutineScope
Adding -Xextended-compiler-checks argument might provide additional information.

Will there be any replacement for Arb.distinct and distinctBy?

Is there any way to use one arb's result to feed the function params for another arb and make a pair out of them (arb1, arb2 cartesian product)?

Any reason why

fun <A : Any> Arb.Companion.choose(a: Pair<Int, A>, b: Pair<Int, A>, vararg cs: Pair<Int, A>): Arb<A>

is

A: Any

? It seems like it can't choose from a null?

This is a very nice feature in jqwik: https://jqwik.net/docs/current/user-guide.html#collecting-and-reporting-statistics also the way assumptions return an error if too many possibilities were skipped: https://jqwik.net/docs/current/user-guide.html#assumptions and in general, having some stats printed like there would add tons of value to property testing in kotest... it would make it much easier to make tests.

I am trying to test a grpc spring boot service. Getting

No qualifying bean of type 'org.lognet.springboot.grpc.autoconfigure.GRpcServerProperties'

What am I missing?

Is there a guide anywhere for using mockk and kotest together? I am trying to convert some tests that use

@Mock

etc... annotations with `MockKAnnotations.init(this, relaxUnitFun = true)`` and haven't found a good way of doing it yet. I have been using

BehaviourSpec

to implement the tests