@sam qq just to clarify my understanding, am i right to understand that spring listener will try to boot up spring before each spec class that summons the bean autowiring?

Do the kotest tests generally run on *nix? I'm getting a failure in

Blonde("foo", true, 23423, Paths.get("a/b/c"))

printing as

Blonde(a=foo, b=true, c=23423, p=a\b\c)

but the tests expect

Blonde(a=foo, b=true, c=23423, p=a/b/c)

- would I break something by changing the static string to use

File.separator

so these tests work on windows as well? Or am I missing something here 🤔 I'm a little wary since I'm changing the clue code which seems related. https://gist.github.com/jschneidereit/251bc1392639ff18741bcb2a844e9fea

Similar deal,

shouldBeSymbolicLink should check if file is symbolic link

blows up in windows unless the test suite is running as admin. The easiest thing to do would be to just disable this test in windows. Possible solutions are to just disable this test in windows or check if the process is running as admin on windows using something like this: https://stackoverflow.com/a/10654463 (it works in the kotlin REPL but the SO comments make it sound like it's not a sure thing)

does kotest support mapping like strikt?

val subject = Pantheon.NORSE
expectThat(subject)
  .get(Pantheon::ruler) // reference to a property
  .get { toString() }   // return type of a method call
  .isEqualTo("Odin")

I’m in the process of migrating some tests from Spek to Kotest, and I’m running into a problem where gradle won’t execute my kotest specs when I have include the spek test engine. Has anyone ran into this before? Right now it seems I can either execute either spek or kotest but not both.

Hi, I am in the middle of convincing my colleagues to use kotlin with kotest instead of groovy with spockframework for testing. One point was that spock has a nice framework with the key workd `given`/`when`/`then`/`expect`. Is there anything similar to this for kotest as well?

Since the last kotest plugin update I cannot start the whole testclass anymore. Before I could do that. What do I have to do in order for that to work again? Same behaviour with freespec describeSpec and behaviourspec 🤔

I’m probably being thick, but I’m finding that I don’t get nice coroutine stacktraces in IntelliJ when my test fails in an

eventually

block. VM options:

-ea -Dkotlinx.coroutines.debug=on -Dkotlinx.coroutines.stacktrace.recovery=true

(belt, braces, stapled on to stomach).

Good news for Android devs using Kotest: work in progress on LiveData assertions and extension listener! 😄

How does Kotest discover tests? Does it scan entire classpath or just the classes from the tests source set? Is it configurable somehow, if we want to only scan classes under specific package?

Another topic: is it a known issue that inline classes don’t work well in forall? Or maybe it’s something wrong with our setup (I don’t see what it could be though)

i wonder what “data driven tests” add to the table. can’t i just use

listOf(
       PythagTriple(3, 4, 5),
       PythagTriple(6, 8, 10),
       PythagTriple(8, 15, 17),
       PythagTriple(7, 24, 25)
    ).map{ (a, b, c) -> test("test %a %b %c") { ...}

in a fun spec?

When I try to set isolationMode on Project level, it does not seem to count I have the following configuration

object KotestConfig : AbstractProjectConfig() {

  override val isolationMode = IsolationMode.InstancePerTest

  override fun listeners() = listOf(SpringListener)
}

But when I set a break point in a test I can see that isolationMode is actually null. Also tried to use the deprecated function, same result. I can also see that the mode is not working as I have one test bleeding into the other. With the listeners it seems to work as the Spring tests are running without having the spring listener added Any idea what I am doing wrong?

I can’t seem to be able to enable logging for Kotest 😕 Any idea what I may be missing? I want to see logs in console when running tasks, I tried: • setting

systemProp.KOTEST_DEBUG=true

in

gradle.properties

•

tasks.withType(Test) { systemProperty("KOTEST_DEBUG", true) }

• exporting KOTEST_DEBUG env variable in console • passing -DKOTEST_DEBUG=true in ./gradlew params

Hi, I’m using FreeSpec style in my project, I reached +1400 lines of test code in one test class, the problem is IntelliJ became super slow and unresponsive when I want to add any new test to that test class, does it have to do with style or ? any ideas?

Hi is there any multiplatform project available where I can see how to configure kotest as multiplatform. I am working on a full stack web application but cant seem to make kotest work for commonTest module

Does the kotest annotation spec respect inner classes? I ended up using them in my test suite similar to

context

in other kotest spec styles. 🤔

Does anyone else notice extremely poor performance of IntelliJ IDEA when editing kotest files? All versions I've tried. I'm not sure what it is about the kotest files that it doesn't like...

When I use tags in IntelliJ by specifying VM options:

-Dkotest.tags="UnitTest"

the report with test results includes test classes that were not tagged. They are listed at the end of report as single line per class, i.e. no specific tests are reported. I tagged test classes, so AFAIU the specs should not even be instantiated (and they aren't when I use tags in Maven). Is this UX bug?

I'm looking for

SkipTestException

in kotest 4.3.0, but I cannot find it. Has it been removed from the code base?

are all kotest styles affected by the IDEA slowdown?

Is there an opposite to

collection shouldExist { … }

? I want to test that the collection does not contain an element matching the predicate

trying to help out with the junit5/quarkus stuff but can’t even get master to build.

❯ ./gradlew build

> Configure project :
Kotlin Multiplatform Projects are an Alpha feature. See: <https://kotlinlang.org/docs/reference/evolution/components-stability.html>. To hide this message, add 'kotlin.mpp.stability.nowarn=true' to the Gradle properties.


> Task :kotest-assertions:kotest-assertions-shared:compileCommonMainKotlinMetadata FAILED
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/Retry.kt: (10, 8): Unresolved reference: kotlinx
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/Retry.kt: (83, 7): Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public operator fun <T, R> DeepRecursiveFunction<TypeVariable(T), TypeVariable(R)>.invoke(value: TypeVariable(T)): TypeVariable(R) defined in kotlin
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/timing/Eventually.kt: (4, 8): Unresolved reference: kotlinx
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/timing/Eventually.kt: (51, 7): Unresolved reference: delay
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/timing/continually.kt: (4, 8): Unresolved reference: kotlinx
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/timing/continually.kt: (34, 7): Unresolved reference: delay
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/until/until.kt: (4, 8): Unresolved reference: kotlinx
e: /Users/tyler.thrailkill/dev/code/oss/kotest/kotest-assertions/kotest-assertions-shared/src/commonMain/kotlin/io/kotest/assertions/until/until.kt: (82, 7): Unresolved reference: delay

I don’t see any kotlinx dependency declared, so how is this building successfully with github actions?

how do i configure kotest to run without junit in gradle and idea? what dependencies do I use?

Is there a way to tell IntelliJ Kotest plugin to use maven-failsafe-plugin configuration for running integration tests (the same as in maven) instead of maven-surefire-plugin configuration?

Hi there! Has anyone observed "weird" behaviour when combining

assertSoftly

with

shouldNotBe

? I just upgraded from the old kotlintest to kotest:4.3.1 and now some of my tests fail. When I remove the surrounding

assertSoftly

block then everythings is fine again. The assertions stay the same but do no longer fail! It also seems to only happen when I use

shouldNotBe

Any idea? Thanks!

“You can ask Kotest to run specs in parallel to take advantage of modern cpus with several cores by setting the parallelism level (default is 1).. Tests inside a spec are always executed sequentially.” is that still true?

i have a really strange classloader problem, here is a reduced test case:

package r2dbcfun

import io.kotest.core.spec.style.FunSpec
import java.io.StringReader
import kotlin.reflect.full.declaredMemberProperties

class Ko2Test : FunSpec({
    listOf(1).forEach {
        context("running") {

            autoClose(StringReader("blah"))
            context("ctx") {
                data class K(val name: String)

                K::class.declaredMemberProperties
            }
        }
    }
})

I was able to reproduce the issue described above. Please have a look at the comment on the original post. What should I do now? File a bug? If so where and how? Thanks!