how hard is it to install an old version of the kotest plugin? i accidentally updated it and now i can't run any tests (since my kotest lib version is too old)

Hi, can i use kotest in common module of Kotlin MPP? I’m specially interested in its styles and data-driven testing

I've set

globalAssertSoftly

to true for my tests but have found a situation where I don't want to use this - is there a way to not use soft assertions for an individual test, or to stop the test after a specific assertion? I've tried

exitProcess(0)

but this leads to the test being terminated without any information about the assertion.

if i have the same context in multiple test classes these contexts are grouped in the test runner. is that a feature?

class Functional1Test : FunSpec({
    context("ctx") { 

different file: 
class Functional2Test : FunSpec({
    context("ctx") {

Great work on Kotest! I have a little question:

data class Person(
    val name : String,
    val age : Int
)

fun Arb.persons() = bind(
    string(), int()
) { name, age -> Person(name, age) }

@Test
fun test() = forAll(
    config = PropTestConfig(
        shrinkingMode = ShrinkingMode.Bounded(10)
    ), 
    Arb.persons()
){ it.age > 18 }

How can I use//create a shrinker for Person?

Idea now complains about one of my test classes, but it compiles and runs fine.

Hello! After upgrading the Kotest version to 4.3.1 (from 4.2.2) I have noticed that it takes double the time to run the tests. I am heavily using the property based tests and I see that now there are much more edge cases. I was told that using a

filter

can be the cause of slowing down. Do you also think that using

bind

is the problem? Maybe I should try to avoid both and use

arbitrary

instead of

bind

?

Hey everyone, Does anyone know if there is an easy way to profile how long tests take to run? I ran Gradle

--profile

, but that only shows the length of the whole suite. I'd like to generate a small report to see which tests take excessively long.

Does anyone know what artifact to use for MPP JVM + JS setup?

Also getting this on kotest-framework-engine@4.3.1:

Cannot access 'kotlinx.coroutines.CoroutineScope' which is a supertype of 'io.kotest.core.spec.style.scopes.GivenScope'. Check your module classpath for missing or conflicting dependencies

Anyone knows a workaround?

What is the compatibility matrix for Kotest vs Kotlin? Is latest Kotest 4.3.1 expected to work with any Kotlin? When I use Kotest 4.3.1 + Kotlin 1.3.72 using inspectors, e.g. forOne fails with java.lang.NoClassDefFoundError: kotlin/KotlinNothingValueException. I am not sure if this is a bug or I am using wrong combination of versions.

Sorry for bothering... The test in ShrinkingTest fails for me. (I'm getting one line with the original cause, but no shrinking-steps.) My question is: is this a know bug? The reason I'm asking is that I couldn't find an issue about shrinking not working.

Hello, i have a problem with migration from swagger to openapi with spring-boot app. The app after migration works fine, but kotest not working at all after it. I am using spring-boot 2.3.4 and kotest 4.2.2. There is no errors spawned when i run tests in idea, just

Test framework quit unexpectedly

. When i run mvn test i get

java.util.ServiceConfigurationError: org.junit.platform.engine.TestEngine: Provider io.kotest.runner.junit.platform.KotestJunitPlatformTestEngine could not be instantiated

.

Any examples of kotest working with KMM? Specifically I wanna test my common/shared code but I didn't succeed into adding kotest dependencies into my project.

Does kotest-property supports Kotlin/Multiplatform? The docs says yes but no artifact found when adding the dependency...

Hey guys 👋 Does anyone know if it’s possible to have kotest and junit5 tests coexist? I have a project with kotest setup and I wanted to give junit5 a go in Kotlin, but when I added

testImplementation(platform("org.junit:junit-bom:5.7.0"))
    testImplementation("org.junit.jupiter:junit-jupiter")

tests are not picked up by Gradle. Do Jupiter and Kotest not like one another?

Hi all, If this is not the place, you can tell and I will remove my question. In the past I saw a video about testing, where they isolated the path that only the failing test touched. By isolating that path, it should be easier to view which code is incorrect. At this moment, I can't find any information about this. Does anyone have more information about this, such as a name, or even better, where I can find how to do this?

Is there a way to build a combination of

Arb

with frequencies like `Arb.choose` which takes into account all the edgecases of all provided

Arb

? I just encountered a bug that was happening on an edgecase value but it only arises when I raise iterations to 100K or so, using the following Arb.

If I'm making an abstract base class for tests that need a testcontainers db connection (in Micronaut Test), is there some kind of generic test type I can use, and then just use whichever of the styles in the actual tests inherited from it?

hi, suddenly i’m unable to run individual tests/suites in IntelliJ any longer, it says:

Test events were not received

, I believe this started happening after update to latest IJ yesterday (for code with me)

Or, better question, how do I get a "ContainerScope" inside a StringSpec?

I'm playing with kotest but it seems to be missing watchosarm32? https://repo.maven.apache.org/maven2/io/kotest/

Is there only supposed to be one

context

as root in a

ShouldSpec

when using

beforeEach

? It seems like when I put the

beforeEach

in the

init

block along with two

contexts

, it only gets run once...

Ok...

beforeTest

and

afterTest

works... but what's the difference? It sounds from the docs that

beforeEach

should be called before each test case with the type

Test

,

should

isn't a

Test

?

When testing things I'm for sure are flaky, like dynamoDB

I don't know if it's possible, but it would be great to somehow attach an execution when shrinking completed, such that an additional run can be made, but where all the loggers are enabled.

One thing I miss about the now-deprecated

shouldBeInstanceOf

that took a block was that I ended up doing things like this:

someList.first().shouldBeInstanceOf<Foo> {
  // 'it' is cast to 'Foo'
  it.someMethodOnFoo() shouldBe ...
}

whereas now I end up doing something like

with (someList.first()) {
    shouldBeInstanceOf<Foo>()
    someMethodOnFoo() shouldBe ...
}

and I prefer the first style, but perhaps just a personal preference.

i was thinking why tests are defined in classes instead of just in top level, and i guess the main reason is discovery. but why are they classes and not objects?

if i create a new project and add only

testImplementation("io.kotest:kotest-framework-engine-jvm:$kotestVersion")

as dependency (and the kotest gradle plugin), i get this compiler error:

> Task :compileTestKotlin FAILED
e: Supertypes of the following classes cannot be resolved. Please make sure you have the required dependencies in the classpath:
    class io.kotest.core.spec.style.scopes.ContainerScope, unresolved supertypes: kotlinx.coroutines.CoroutineScope
    class io.kotest.core.test.TestContext, unresolved supertypes: kotlinx.coroutines.CoroutineScope