In the assertion library, we have access to both:

infix fun <A : CharSequence> A?.shouldMatch(regex: String): A
infix fun <A : CharSequence> A?.shouldMatch(regex: Regex): A

Is there a reason for having only the negation for the String parameter?

Hey there, I don't mean to rush, I just wanted to ask about a plan for the 5.1 release with support for Coroutines 1.6. I wanted to use the latest SNAPSHOT, but it doesn't seem to have

iossimulatorarm64

binaries

Kotest 5.1.0 has been released. https://kotest.io/docs/changelog.html

Hi everyone, I've just started working on an app (which has many architecture and code quality problems) without any tests and after comparing test frameworks I think Kotest would be my favourite. I've been having some difficulties with setting it up though, mostly in the dependencies department. I wanted to know if the [getting started guide](https://kotest.io/docs/quickstart/) is still up to date and complete. Do I not need any other dependencies than these listed below for unit testing with kotest, with the kotest assertions?

testImplementation 'io.kotest:kotest-runner-junit5-jvm:5.1.0'
testImplementation 'io.kotest:kotest-assertions-core-jvm:5.1.0'

Currently my test dependencies look like this (yes with all the comments... don't worry, I didn't commit it yet)

//    testImplementation 'junit:junit:4.12'
    testImplementation 'io.kotest:kotest-runner-junit5-jvm:5.1.0'
    testImplementation 'io.kotest:kotest-assertions-core-jvm:5.1.0'
//    testImplementation 'io.kotest:kotest-assertions-json-jvm:5.1.0'
    testImplementation 'io.kotest.extensions:kotest-extensions-robolectric:0.5.0'
    implementation "org.jetbrains.kotlin:kotlin-reflect:$kotlin_version" // M: Why do I need this? ask in the kotlin kotest channel
//    testImplementation 'org.json:json:20180813' // M: needed for using JSONObject in unit tests, which is part of the android framework
//    testImplementation 'com.googlecode.json-simple:json-simple:1.1.1' // M: needed for using JSONObject in unit tests, which is part of the android framework
//    testImplementation 'org.robolectric:robolectric:4.6' // M: use kotest robolectric instead

//    testImplementation "de.mannodermaus.gradle.plugins:android-junit5:1.8.2.0"
    // (Required) Writing and executing Unit Tests on the JUnit Platform
//    testImplementation "org.junit.jupiter:junit-jupiter-api:5.8.2"
//    testRuntimeOnly "org.junit.jupiter:junit-jupiter-engine:5.8.2"

    // (Optional) If you need "Parameterized Tests"
//    testImplementation "org.junit.jupiter:junit-jupiter-params:5.8.2"

//    androidTestImplementation 'com.android.support.test:rules:1.0.2'
//    androidTestImplementation 'com.android.support.test:runner:1.0.2'
//    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

I'm using robolectric here because I wanted to test something with json but apparently that's part of the android platform and couldn't get it to work by including json dependencies separately. I had to include the kotlin-reflect library, however I'm not doing any reflection. Why do I need this dependency? Where is it using reflection? At this moment I'm having following error about androidx.

This project uses AndroidX dependencies, but the 'android.useAndroidX' property is not enabled. Set this property to true in the gradle.properties file and retry.
The following AndroidX dependencies are detected: androidx.test:monitor:1.4.0, androidx.annotation:annotation:1.1.0

Where is androidx used? Why do I need to add this? I do not see any references to androidx in our codebase. I suppose I will add it but I want to understand it. I was wondering if I also should include the mannodermaus plugin for junit5 and the junit dependencies or those are covered by kotest already or are those not relevant for kotest? Most of my android knowledge dates from around 2015. If someone can shed more light on the things above, that would be great! I'm happy to be working on Android again! 😄

I upgraded the Kotest version from <kotest.version>4.6.4</kotest.version> to <kotest.version>5.1.0</kotest.version> in my maven pom. and now I'm getting the following error. this is a spring boot project with 100% Kotlin.

@LeoColman Did something change in the Robolectric extension? I started getting

No instrumentation registered! Must run under a registering instrumentation.

... I'm using kotest 4.6.4 and tried the 0.5.0 and 0.4.0 extensions...

Is there a way to run regular JUnit tests in the same test module as Kotest 4.6.x tests? (see thread for exception I'm getting...)

Is there any way that in the same test I have these two assertions, first one passes second one fails? Don't get it...

o1 shouldBe o2
(o1 == o2) shouldBe true

Hey - When updating to

5.1.0

I noticed that the documentation points out a deprecated way to add the junit_xml reporter to the ProjectConfig. I opened a PR here: https://github.com/kotest/kotest/pull/2801

Hmm - after updating to KoTest 5.1.0 I have a problem that tests do not start to run when I set

parallism

to something else than 1. It worked before - is anyone having the same problem, or is this something specific to the project I am working in? 🤔

Hey guys! Any particular reason for the extensions page to not be listed alphabetically? I think it would be easier to find what we want

Hello, I don't understand the versioning of the many kotest modules For example https://repo.maven.apache.org/maven2/io/kotest/kotest-assertions-ktor/ is at 4.4.3 https://repo.maven.apache.org/maven2/io/kotest/kotest-core/ is at 4.1.3 https://repo.maven.apache.org/maven2/io/kotest/kotest-assertions-json/ is at 5.1.0

I have a test suite that uses multiple junit engines, and when i run tests by uniqueId kotest also runs tests even when the uniqueId clearly states a different engine than kotest.

[engine:failgood]/[class:...]/[class:...]

I think kotest should just run no tests when the uniqueid selector is used with a different engine.

Just updated from v5.0.3 to 5.1.0 and now I’m getting

java.lang.NoClassDefFoundError: kotlinx/coroutines/test/TestDispatcher

all over the place when i run my test set. Using Kotlin 1.6.10. I don’t have anything that is explicitly drawing in that coroutine package.

Hello! Trying to write data-driven-tests as described in the manual, but none of the below finds

withData

, unresolved reference. Was there an api change? This is

5.1.0

class JobFlowCombinatorsTest : ShouldSpec({
  context("state merging") {
    withData() {}
  }
  should("correctly combine states") {
    withData() {}
  }
})

Is there a way in the kotest intellij plugin to set junit’s setForkEvery? I’d like to force a new jvm for each spec if i can. I can do it when running from the cli, but it doesn’t appear that the kotest extension respects the build.gradle.kts config?

I'm trying to use kotest with coroutines and robolectric, so I have this simple test:

@RobolectricTest
class RoboTest : StringSpec( {
    "test" {
        println(1111111)
        delay(500)
        println(22222)
        1 + 1 shouldBe 2
        println(3333)
    }
})

But it never finishes! It prints 11111 and then just hangs. Any idea why?

Hi, I'm trying to get the robolectric kotest extension working on my android project but I'm running into this error when running the test:

java.lang.IllegalStateException: No instrumentation registered! Must run under a registering instrumentation.

I searched around for an example project or usage and came up blank. Is there a sample project out there?

Im not sure if this is a kotest problem, or my understanding of map/combine is lacking, but Im struggling to understand why combine does not work as expected in my tests… Basic example in 🧵

Hi all. I'm new to Kotest, but I am loving it. I'm writing a library that needs to be cross platform so using MPP, and Kotest for my all my tests. I can't seem to run my tests in iOS because of a linking error, and was hoping to get some help.

> Task :my-library:linkDebugTestIosX64 FAILED
e: Could not find "io.kotest:kotest-assertions-api" in [ ... ]
FAILURE: Build failed with an exception.

// kotestVersion = "5.1.0"
commonTest {
    dependencies {
        implementation "io.kotest:kotest-framework-engine:${rootProject.ext.kotestVersion}"
        implementation "io.kotest:kotest-assertions-core:${rootProject.ext.kotestVersion}"
        implementation "io.kotest:kotest-property:${rootProject.ext.kotestVersion}"
        implementation "io.kotest.extensions:kotest-assertions-arrow:1.2.2"

        runtimeOnly "io.kotest:kotest-assertions-api:${rootProject.ext.kotestVersion}"
    }
}

Tried to write a test with

testCoroutineScheduler

in

commonMain

in a KMP project and it seems that it is defined only form jvm projects. Is there some reason to restrict to jvm-only?

Hi, is the Robolectric kotest extension abandoned?

Hi there, I’m currently starting to integrate the Kotest runner in our test suite as we are really happy with the already used assertions library. It seems like Kotest 5.1.0 is not working with Spring 2.6.3 Webflux, since Webflux seems to drag in

org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm:1.5.2

(even though we specified the dep as 1.6.0) and Kotest required

1.6.0

. Having both

1.6.0

and

1.5.2

of

corouitnes-core

on the classpath seems not to work. Did anybody else run into this problem? Right now downgrading to

5.0.3

is the only solution I could find. Any help is appreciated. Thanks!

I’m trying to debug some tests that use

shouldContain

, but the assertion failure messages only include the first five elements. Is there a reason for this? It’d be great if the error included the full list, or if there was some way to configure this behaviour

Hey folks, (I am new to the channel and I hope this is the right place to ask). I am getting this exception when running Kotest on a gradle travis-ci build but not when I run it on my local mac book:

UnknownClass.Kotest > UnknownClass.initializationError FAILED
    java.lang.UnsupportedClassVersionError at ClassLoader.java:-2

(see log here). I am using Kotlin 1.6.2 and Kotest 5.10 (see versions here) I am a little unclear how to debug this and any pointers are greatly appreciated.

Hey guys! Can I get a review at https://github.com/kotest/kotest-extensions-mockserver/pull/1?

How can I use Kotest with Android Instrumentation test (

androidTest

)? I don't need to test UI, just Room database. It seems my tests are not even run. Or maybe it does, I don't know. But the result of

connectedDebugAndroidTest

is success, even when there is a test that must be definitely failing.

👋 I found a problem when doing an assertion on a nullable variable e.g.

nullableThing?.shouldBe(something)  // This works
nullableThing?.shouldBeGreaterThan(something). // This doesn't work

If nullableThing is null the safe call stops the assertion from being called, so the tests passes when it shouldn’t. I found two ways to fix this but neither seem ideal to me: • Add another assertion to check that the thing isn’t null e.g.

nullableThing shouldNotBe null

• Use

!!.

instead of

?.

but this gives a null pointer exception when the test fails which could lead to confusion Is there a better way to deal with assertions on nullable variables?

I hit the strong encapsulation issue using the system extension

withEnvironment

on JDK 17.

java.lang.reflect.InaccessibleObjectException: Unable to make field private final java.util.Map java.util.Collections$UnmodifiableMap.m accessible

at

SystemEnvironmentExtensions.kt:115

. I can get around the issue by adding

--add-opens java.base/java.util=ALL-UNNAMED

, but I'm wondering if there's a different path forward for this feature that doesn't require the workaround.?