I’m getting

No tests found for given includes

when trying to run a single kotest test inside a gradle project--I assume this must be something dumb I’m missing but after googling around a bit I still haven’t seen anything that addresses it. I do have

tasks.withType<Test>().configureEach {
    useJUnitPlatform()
}

in build.gradle.kts

I have just published an article that can help you get started with Property Based Testing. https://ericampire.com/create-powerful-tests-using-property-based-testing

Anyone have any luck running kotest on kotlin native?

Is there any way to run a JUnit test class when using kotest? We have an abstract base class that defines lifecycle/tests for a component using JUnit5 (from a library we don’t control) but we’re using kotest in our project.

Are there any known issues with setting

assertionMode

to

Error

and tests that use coroutines? My test uses coroutines and makes assertions (and the test fails if the assertions fail), but I still get a

Test … did not invoke any assertions

error.

Hello everyone, I have a question about Kotest; all the documentation examples use (public) classes, such as

class MyTest: SomeSpec({ ... })

But in e.g. vanilla JUnit classes are always recommended to be internal (package private) and I found out that this works as well:

internal class MyTest: SomeSpec({ ... })

Is there a reason test classes should be public or can/should they be internal?

Hi folks, when you read a book on testing it often says that a test must be repeatable In the case of property based testing, the data is generated automatically, can we say that these tests are repeatable?

Good evening! Does Kotest have a default test filter? I've updated from 4.6 to 5.3 and now a test class named

ConfigTest

is being run as part of my integration tests. I have no explicit test filter in gradle telling it to pick up

*Config*

as part of the integration test task, so I'm at a complete loss as to why this is happening after updating Kotest.

I'm porting some unit tests from Kotest 4.6 to Kotest 5.3, and I've discovered that one of my tests is taking a hugely longer time to run with the new kotest - i.e. from 1.5 seconds with kotest 4.6, to 90 seconds with kotest 5.3 on my test AWS host. Any idea what could be causing this?

Hello, how is the best way to do this with kotest?

val item = turbineState.awaitItem()
item.showProgress.shouldBe(false)
item.selectedItem.shouldBe(-1)
item.filteredLocations.count().shouldBe(2)

I tried this code but is not working...

turbineState.awaitItem().should {
   !it.showProgress &&
   it.selectedItem == -1 &&
   it.filteredLocations.count() == 2
}

Is it possible to attach logs to a test case/result from a

TestListener

?

🎩 Quick question, is support for IJ 2022.2 EAP planned?

I added a massive hack to make it work. There is zero chance gradle fix the bugs. They simply don't care.

I'm writing a selenium test in kotest - I'm implementing a

TestListener

so that if

TestResult.isErrorOrFailure

I can use

RemoteWebDriver.getScreenshotAs

to capture the output. However, I need to save the file somewhere... is there a way to work out an output directory for kotest? I guess it would be very dependent on how kotest was bring run (gradle, maven, stadalone, whatever), so probably not, but thought I'd ask if anyone had any bright ideas.

Another q - is there a way to declare that a listener depends on another listener so it's beforeTest happens after, and it's afterTest happens before, the methods on the other listener?

Hello, is using

runTest

still needed when using Kotest with

testCoroutineDispatcher = true

? Context : I would usually have a class with

coroutineScope: CoroutineScope

in the constructor

class MyClass(private val coroutineScope: CoroutineScope): CoroutineScope by coroutineScope { }

then in my test I would do something like this :

"myTest using string spec" {
    runTest {
        val myClass = MyClass(this)
    }
}

So that it uses the Coroutine scope from

runTest

. I see that

StringSpec

has a test scope so that I can do the same but without wrapping my test with

runTest

, is it safe to do so? I want to ensure the are no coroutines leaks between test to avoid flaky tests.

"myTest using string spec" {
    val myClass = MyClass(this)
}

Just bumped to Kotlin

1.7.0

and am seeing this in Kotest:

Found interface kotlin.time.TimeMark, but class was expected
java.lang.IncompatibleClassChangeError: Found interface kotlin.time.TimeMark, but class was expected
	at io.kotest.engine.spec.interceptor.SpecFinishedInterceptor.intercept-0E7RQCE(SpecFinishedInterceptor.kt:37)
	at io.kotest.engine.spec.interceptor.SpecFinishedInterceptor$intercept$1.invokeSuspend(SpecFinishedInterceptor.kt)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)

do I need to wait for a new Kotest version? ** Not a contribution

Hi, all) want to use envs in tests but faced some problems, can you please help? More details in stackoverflow question. https://stackoverflow.com/questions/72586298/kotest-change-environment-variables

Hi, community. Can someone help me? I need an example of using Kotest with PiTest for JDK 1.8. The extension 'kotest-extensions-pitest' requires JDK 11.

Hello ppl. Is there anyway to get transactions to rollback for tests in kotest + spring without using annotationSpec?

Hello everyone. I wanted to ask you something related to Kotest. I have been having issues lately that when I run my unit tests with kotest everything is green, but if I explore the builds I get some errors but I can't know about the build errors unless I explore the build output on my tests. I noticed that my tests failed in the CI that's how I discovered this issue. In the few places that this happened was because the class had some code in the init block. I wanted to know if there exists any flag or any way to make the tests fail locally so I know there are issues before running the CI. Thank you in advance.

👋 I was half expecting kotest to play nice with Junit5 extensions (such as Selenium-Jupiter) with at least

AnnotationSpec

but it doesn't appear kotest supports

ParameterResolver

(Junit docs). Am I understanding this correctly?

hi @sam, kotest provides the `shouldMatchEach`matcher for collections. We found it helpful to have a similiar matcher for Maps and implemented it on our own.

fun <K, V> Map<K,V>.shouldMatchAll(vararg matcher: Pair<K, (V) -> Unit>)

Do you think this is generally helpful and would you accept a PR with that matcher?

🎩 I don’t intend to rush, but I wanted to ask if there’s some rough estimate for https://github.com/kotest/kotest/issues/2915? I don’t know how complex the issue is and I don’t understand the framework enough to contribute, I’d just like to know, if possible, rough timeline to know how to plan my work 🙂 Also I’m wondering if it has something to do with other issues related to tests naming like https://github.com/kotest/kotest/issues/3068

Hey folks! Anyone got examples of code Katas using kotest? I haven’t been able to find any so far…

Does beforeSpec work for js tests? This test actually runs and fails with

IllegalStateException: IN TEST

. The same test in jvm works as expected failing with

IllegalStateException: IN BEFORE SPEC

class SimpleTest : FunSpec({
    beforeSpec {
        error("IN BEFORE SPEC")
    }
    test("test") {
        error("IN TEST")
    }
})

Hi! Bumping from kotest 5.0.0 to 5.3.1, I now have kotest complaining that "Nested tests are not supported" when running my tests on JS target. I understand the explanations @sam gave about the

describe

levels not supporting async lambdas in JS test frameworks. Now I need to understand why we need to have non-test-case levels suspending on the Kotest side?

I recently upgraded to Kotlin 1.7.0 & Kotest 5.3.1, and I'm now getting a strange error. I don't understand why it's trying to pull in

kotlinx-coroutines-bom:jar

, which obviously wouldn't exist (pom only).

Could not find artifact org.jetbrains.kotlinx:kotlinx-coroutines-bom:jar:1.6.3

This probably isn't an error with Kotest, but it's the closest lead I have right now.

I'm generating with tiny types, getting

the target size requirement of 63 could not be satisfied after 630 consecutive samples

This is the type I'm generating, both fields are enum classes:

data class PollingSettings(val polling: EnumSet<AutomaticPPICPolling>, val interval: PICCPollInterval)

Reducing the number of iterations didn't help

Does Kotest have the equivalent of AssertJ's

extracting

feature? For example, in AssertJ I can do this:

assertThat(foo)
    .extracting(Foo::id, Foo::description)
    .containsExactly(1234, "this is a foo")

The closest I could find was

shouldBeEqualUsingFields

but that's not suitable, as it requires another Foo argument which I can't easily construct; I only have the naked property values.