well I added some feedback that I wasn't sure if probabilistic edgecases was even needed anymore since we have probabilistic values now :)

@sam I'm having trouble finding how to build the project. I want to work on the Quarkus extension, but can't for the life of me figure out which gradle tasks I should be building.

Is there a maven bom for Kotest?

So I made a PR for the quarkus extension examples, https://github.com/kotest/kotest-examples-quarkus/pull/1/files It demonstrates that the kotest tests aren't picked up when running

./gradlew test

. For the QuarkusMockTest it shows that 'Test events were not received'. For all the kotest tests, if you run the individual test (not the whole class) directly in intellij, it throws an error about the property not being initialized.

Hello guys, Sorry for probably dummy question, however do I need to install Kotest Plugin into my local IDEA IDE to be able to run tests from IDEA directly?

Hello Kotest magicians, I'm looking into the Kotest and trying to understand the best practices The Groovy Spock is the main testing framework for me at the moment, and I like it a lot. However, the groovy dependencies generate an unreasonable level of discomfort in my kotlin projects. Therefore I'm looking for a replacement and Kotest looks awesome and super promising. But I can find good examples for Data Driver Testing with Kotest. https://spockframework.org/spock/docs/1.0/data_driven_testing.html My perfect scenario will be the next one: • Keep the usage of

Given When Then

- it is covered by

BehaviorSpec

• Usage of something similar to

Data Tables

from Spock but in Kotest -

io.kotest.data.forAll

looks similar Can anyone please point me to any well written example? Because I end-up with a

callback hell

all the time Thank you in advance!

Ok, another dumb question: when upgrading from 4.1.3 to 4.3.2, I seem to have lost the String matchers. the package

io.kotest.matchers.string

isn’t resolving, which is weird, because from what I’ve seen in github it doesn’t look like that changed? I also didn’t see any mention about a dep change for the matchers in the changelog, but maybe I missed that. Sorry, it was intellij weirdness…reopening the project fixed it 🤷‍♂️

Is the kotest-bom working? There are already quite a few modules in kotest and some have different versioning...

I'm trying to setup kotest but no matter what my IDE (intellij) does not suggest the Specs for import. In both the parent and children module I have all the runner, assertions and property imports as

testImplementation

. Am I missing something obvious?

Hey, guys! Does anyone know is it possible to force StringSpec tests run with runBlockingTest, not with runBlocking?

Small feedback: I just updated Kotest from 4.4.0 to 4.4.3 and some of my tests started failing because of this change: https://github.com/kotest/kotest/commit/650e00befec2a6320fd9bc5eb3d921de759230e8#diff-8e93023b4ef7e14183574357e70[…]0aa56f52830450b7824903dc5c4a4cf0. It’s not documented in the Github releases (I later realized proper changelog is at https://kotest.io/docs/changelog.html), so you might consider: • bumping minor version for behavior changes. This change was categorized as a bugfix, but throwable matchers have worked like this forever • removing content from the Github releases page that looks like a changelog (e.g. https://github.com/kotest/kotest/releases/tag/v4.4.1) and/or linking to actual changelog entry

Gotta say I’m not a fan of that matcher change 😄 Do people really need to check for cause as well? I see we do that only in some places specifically, otherwise causes are pretty much private. And the error message if cause is different is pretty vague because it only includes exception class and message, so I end up with

expected:<com.example.MyException> but was:<com.example.MyException>
Expected :com.example.MyException
Actual   :com.example.MyException

😕

I just noticed Kotest adds transitive dependency on Mockk library. Seems like the only place it’s used is https://github.com/kotest/kotest/blob/99138d177bd52feea19740abeec6c5c4a3ae11c1/kot[…]mMain/kotlin/io/kotest/extensions/time/ConstantNowExtensions.kt. Is it safe to exclude this dependency? I consider mocking static methods, and basically everything Mockk is needed for a very bad practice, and I’d like to avoid accidentally having its agent on the classpath

Oh... it seems like the Kotest robolectric extension doesn't initialize the robolectric classloader and environment when the class is created, so all

val

s at the class level use the original classloader... is this really the only way, or can this be fixed? It seems it's linked to this issue: https://github.com/android/android-test/issues/409

Boy... now I'm confused... that test passed even though I have a

TODO()

in the subject's function being called... by stepping through the code, I see that code is reached, but the test passes... 🤯

The exception seems to get lost in coroutines...

this might be the most stupid question ever, but is data driven tests supposed to work with stringspec?

import io.kotest.core.datatest.forAll
import io.kotest.core.spec.style.StringSpec
import io.kotest.data.Row2
import io.kotest.data.row
import io.kotest.matchers.shouldBe

class ParticipantRoleTest : StringSpec({
  "create from string" {
    forAll<Row2<String, *>>(
      "DamageCauser" to row("DamageCauser", ParticipantRole.DamagingParty),
      "Customer" to row("Customer", ParticipantRole.PolicyHolder),
      "Unknown" to row("Unknown", ParticipantRole.Other),
      "Repairer" to row("Repairer", ParticipantRole.Repairer),
    ) { (input, output) ->
      ParticipantRole.fromString(input) shouldBe output
    }
  }
})

this does nothing, tests are not executed but

import io.kotest.core.datatest.forAll
import io.kotest.core.spec.style.FunSpec
import io.kotest.data.Row2
import io.kotest.data.row
import io.kotest.matchers.shouldBe

class ParticipantRoleTest : FunSpec({
  context("create from string") {
    forAll<Row2<String, *>>(
      "DamageCauser" to row("DamageCauser", ParticipantRole.DamagingParty),
      "Customer" to row("Customer", ParticipantRole.PolicyHolder),
      "Unknown" to row("Unknown", ParticipantRole.Other),
      "Repairer" to row("Repairer", ParticipantRole.Repairer),
    ) { (input, output) ->
      ParticipantRole.fromString(input) shouldBe output
    }
  }
})

generates 4 tests as expected

are you on 4.4.x ?

In 4.5 it will be improved so it works with string spec, but it should be erroring at least now

I just upgraded our environment to Java 11, and now I am getting problems with gradle and kotest. Specially, gradle can’t find any tests to run. I’m sure I have something mis-configured. Has anyone run into this before? And can point me in the right direction before I start fiddling with everything?

Hello, I’m using a kotest 

TestFactory

 and trying to understand the lifecycle. It appears that the 

beforeTest

 /`afterTest` functions are executed but not the `beforeSpec`/`afterSpec` functions. Can someone help me understand why? Code:

val myTestFactory: TestFactory = shouldSpec {
    beforeSpec {
        println("beforeSpec")
    }

    beforeTest {
        println("beforeTest")
    }

    afterSpec {
        println("afterSpec")
    }

    afterTest {
        println("afterTest")
    }

    should("help me understand the factory lifecycle") {
        println("during")
    }
}

class MyTest : ShouldSpec({
    include(myTestFactory)
})

Output:

~~~ Kotest Configuration ~~~
-> Parallelization factor: 1
-> Default test timeout: 600000ms
-> Default test order: Sequential
-> Default isolation mode: SingleInstance
-> Global soft assertations: False
-> Write spec failure file: False
-> Fail on ignored tests: False
-> Spec execution order: SpecExecutionOrder
-> Extensions
  - io.kotest.engine.extensions.SystemPropertyTagExtension
  - io.kotest.core.extensions.RuntimeTagExtension
  - io.kotest.engine.extensions.RuntimeTagExpressionExtension

beforeTest
during
afterTest
MyTest > should help me understand the factory lifecycle PASSED

* Not a Contribution *

Ran into an issue using

Arb.bigDecimal()

. Code:

class MyTest : ShouldSpec({
    should("be able to use bigDecimal") {
        // It would be great if Arb.bigDecimal() actually worked here :)
        checkAll(Arb.bigDecimal()) { bigDecimal ->
            true shouldBe true
        }
    }
})

~~~ Kotest Configuration ~~~
Character I is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
java.lang.NumberFormatException: Character I is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
	at java.base/java.math.BigDecimal.<init>(BigDecimal.java:518)

MyTest > should be able to use bigDecimal FAILED
    java.lang.NumberFormatException at MyTest.kt:33
        Caused by: java.lang.NumberFormatException at MyTest.kt:33

If we look at the implementation of

bigDecimal()

I can see why it’s failing, it’s simply taking

Arb.double()

and calling the

toBigDecimal()

extension function which fails on inputs like

Double.NEGATIVE_INFINITY

and

Double.POSITIVE_INFINITY

. Is this a bug or am I using

Arb.bigDecimal()

incorrectly? * Not a Contribution *

Having a weird issue with Arbs and IOS. Basically Using arbs in iOS tests is resulting in an InvalidMutabilityEcception on XorWowRandom. Something like

Arb.long

is fine but using it in

checkAll

for example or doing something like

arb.long.take(1)

results in the exception I'm using property testing but not the framework.

Hello I was trining to setup my new

KMM

generated project from the

KMM PluginWizard

I don’t know what I miss… here but I cant get it up&running on AS. https://kotlinlang.slack.com/archives/C3PQML5NU/p1618153601483200?thread_ts=1617926247.459900&cid=C3PQML5NU

I wonder if there are any plans in the near future to allow given/and/when/and/then/and tests at the same nesting level... I think this was discussed before as not being easy, but it keeps on eating at me how much nicer the tests could look if it would be possible...

@sam, when you use FunSpec, where do you do AAA (Arrange-Act-Assert)? All in the

test

blocks (using

context

just as a textual description), or spread out in the

context

blocks (possibly with instancePerLeaf)?

hi all, I've recentlly updated to arrow 0.13.1 and facing some issue with the

shouldBeRight {  ... }

function: the error I get:

'java.lang.Object arrow.core.Either$Right.getB()'
java.lang.NoSuchMethodError: 'java.lang.Object arrow.core.Either$Right.getB()'

I have version

4.4.3

for kotest libraries, and updated the intellij kotest plugin (version:

1.1.31-IC-2021.1

) the

shouldBeRight()

function works as expected, only the

shouldBeRight { value -> ...}

fails. Any help is apreciated, thank you!

Hi 👋 If I’ve got a String Arb and I set the minimum size to 1, how can I stop it shrinking to size 0? In this example,

authKey

shrinks to 0, and so gives an invalid reason for failure.

test("expect 'actual code is failing', _not_ authKey length error") {
    checkAll(
      Arb.string(1..10, Arb.alphanumeric()),
    ) {
        authKey,
      ->
      withClue("authKey must have length > 0") {
        authKey shouldHaveMinLength 1
      }
      fail("actual code is failing")
    }
  }

I’ve tried using

Arb.string(1..10, Arb.alphanumeric()).filter { it.isEmpty() },

but then the test loops endlessly

Does kotest support native targets? There is something mentioned in get started but there is no setup show