Take a look at withClue and asClue

can some fix this in high priority? https://github.com/kotest/kotest/issues/1223

as in the rest why asserAll/forAll are not suspend functions?

👋 hello! I have an issue with beta1 kotest version in :android: . if i run

gradlew test

it freezes 🙄 anyone else experienced this issue? I have default config (1 thread). I tried to add custom config but kotest did not pick it up 🤷‍♀️

hi, is it possible to pass some arguments to the tests?

Is anyone getting

java.lang.NoClassDefFoundError: kotlin/time/MonoClock

when running kotest with Kotlin 1.3.70?

Hey guys! I just started with kotest + mockk and instantly faced an issue: since all tests are declared within one big lambda passed to ctor (

StringSpec

), all the mocks I need are declared as local variables inside same lambda and not re-initialized for each test case (like in vanilla JUnit). Essentially it means that the 2nd test can see mock invocations from the 1st one, messing up all verifications. How can I avoid that?

Actually I’m curious, what’s the use case for

InstancePerTest

isolation mode? The way we’re using kotest right now is with

DescribeSpec

, so we have bunch of

describe

and

context

blocks which set up tests for the

it

blocks which contain the assertions. Iiuc,

InstancePerLeaf

will create new instance of the test for each

it

block, and execute everything that leads to it.

InstancePerTest

would create new instance not only for

it

block, but also for

describe

and

context

, is that correct?

Btw, how can I change isolation mode for a single spec, not for a whole project?

@akowal @Tesserakt Kotest Assertions are now available as separate module you can add them in your build file as. “io.kotest:kotest-assertions-core:4.0.0-BETA2” Separating the assertion module help users to use kotest framework independent of assertions

Hey everyone, I’m trying to run a sample test with kotest but it never gets past the

Extensions

step, when I stop the execution it ends saying

Test events were not received

. This is the sample test I’m trying to run…

class SimpleTest : FunSpec({
    test("just a simple test") {
        1 + 1 shouldBe 2
    }
})

is it expected that

class SampleTest : ExpectSpec() {
  init {
    context("test") {
      expect("sum") {
        1 + 1 shouldBe 3
      }
      expect("sum right") {
        1 + 1 shouldBe 2
      }
    }
  }
}

expect("sum right')

is ignored? I am trying to better understand isolation modes, tests and leaves and was a bit surprised by this case, also because changing isolation mode does not affect the result. kotest 3.4.2

In addition to kotest-runner-junit5 you will need the assertion module as well, please have look at https://github.com/kotest/kotest/blob/master/README.md

Hey folks, I've just started using kotest and had a question: • Has anyone been able to get the "<Click to see difference>" dialog with diff window to appear when an assertion fails using intellij? This diff window is super helpful when doing a "foo" shouldBe "bar". This seems to work with the core kotlin.test assertEquals method but the shouldBe, etc all seem to throw a too generic AssertionError which intellij doesn't seem to be able to understand. Any help would be much appreciated

tasks.withType<Test> {
    useJUnitPlatform()
}

In multimodule app this code ⬆️ should be in each module or can be in Project level build gradle file?

minor typo:

object ProjectConfig : AbstractProjectConfig {
object ProjectConfig : AbstractProjectConfig() {

https://github.com/kotest/kotest/blob/master/doc/project_config.md

What gradle version are you using?

Now that version 4 has been released - in there any scope to update the intellij kotlin-test plugin to support this version @sam? https://plugins.jetbrains.com/plugin/11585-kotlintest

Hey, checking out kotest for the first time. Using Android Studio with gradle version 5.6.4, gradle plugin version 3.6.1. In build.gradle (:app) I have

dependencies {
    ...
    testImplementation 'io.kotest:kotest-runner-junit5:4.0.1'
    testImplementation 'io.kotest:kotest-assertions-core-jvm:4.0.1'
    testImplementation "io.mockk:mockk:1.9.3"
    testImplementation 'junit:junit:4.12'
}

as well as

android.testOptions {
    unitTests.all {
        useJUnitPlatform()
    }
}

when trying to mimic examples from the docs I cannot seem to be able to extend any of the Spec classes (just getting unresolved reference) nor use keywords like

shouldBe

. The only package I seem to be able to `import`is

io.kotest.matchers

. Any idea what I am missing? Thanks!

Arch test is junit 4?

Thanks @sam and @LeoColman A couple of follow up questions: 1: If i add a

afterTest {
        println("afterTest called for '${it.a.name}'")
    }

..i get

beforeTest called for 'when container when' of type: Container
afterTest called for 'when container when'
beforeTest called for 'should container should' of type: Container

beforeTest called for 'the tests' of type: Test
testing
afterTest called for 'the tests'

afterTest called for 'should container should'

So it seems like the

When

is completed before (or independently of) its children while the

should

is completing its children before completing itself. Is this an explicit approach or should I just not make to many assumptions regarding the ordering of completions? 2: Do you have a recommended approach for doing setup/teardown scoped on

When

for resources that are to be available for all the Whens children? Not for every

When

in the spec but for a single instance. I'm moving over from Spek 1 where this could be achieved with `beforeGroup`/`afterGroup`. The only approach I have found so far is to factor these cases out into separate specs. Leaf isolation mode would not be optimal since it would recreate the resource for each TEST not for each When. I suspect I need to adjust my expectation as to the contract Kotest offers reg. the relationship between nested containers/tests.

How was this issue resolved? https://github.com/kotest/kotest-intellij-plugin/issues/17 Reason I ask is I'm getting a similar error:

Exception in thread "main" java.lang.NoClassDefFoundError: io/kotlintest/runner/jvm/TestEngineListener

Hopefully a quick question. I'm using Kotest to run my android instrumented tests, and I am currently using

androidTestImplementation('io.kotest:kotest-runner-junit5-jvm:4.1.0.197-SNAPSHOT')

in my build.gradle, but Android Studio is giving me the following error:

org.junit.runners.model.InvalidTestClassError: Invalid test class 'com.bytonomy.tech.nyteout.architecture.test.utilities.ApplicationSettingsSpec':
1. No runnable methods
at org.junit.runners.ParentRunner.validate(ParentRunner.java:525)
at org.junit.runners.ParentRunner.<init>(ParentRunner.java:92)
at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:74)

Is this a known issue with this version?

quick upgrade question. Where did List.shouldContainAll() run off to?

That was quick

Hey guys 🙂 In JUnit running stuff in a test scope is pretty straightforward:

@Test fun someTest = testScope.runBlockingTest { }

. Is there some well-established pattern for running specs in a test scope? For example, do you wrap topmost test block, or maybe each smaller scope separately? Would it make sense if Kotest facilitated (or maybe it does?) running tests with coroutines in a test scope, by allowing injecting it or providing. I don’t think there’s any configuration regarding that though, is there?

4.0.2 has been released

Haven't anyone created a ticket at https://youtrack.jetbrains.com/issues/KT to allow to extract lambda outside the constructor parameters? It will be great to have such a feature for kotest: instead of

class MyTest : FreeSpec({
    // ...
})

it will be possible to write like

class MyTest : FreeSpec {
    // ...
}

Hello! 👋 I am trying to switch our medium-sized Kotlin project from using

kotlintest

to

kotest

. However, we have a grpc project, where Kotest is having some issues. Has anybody seen this? Would you have suggestions on how to fix it?

* What went wrong:
Execution failed for task ':integration-grpc-server:extractIncludeTestProto'.
> Could not resolve all files for configuration ':integration-grpc-server:testCompileProtoPath'.
   > Could not resolve io.kotest:kotest-runner-junit5-jvm:4.0.2.
     Required by:
         project :integration-grpc-server
      > Cannot choose between the following variants of io.kotest:kotest-runner-junit5-jvm:4.0.2:
          - jvm-api
          - jvm-runtime
          - metadata-api
        All of them match the consumer attributes:
          - Variant 'jvm-api' capability io.kotest:kotest-runner-junit5-jvm:4.0.2:
              - Unmatched attributes:
                  - Found org.gradle.status 'release' but wasn't required.
                  - Found org.gradle.usage 'java-api' but wasn't required.
                  - Found org.jetbrains.kotlin.platform.type 'jvm' but wasn't required.
              - Compatible attribute:
                  - Required org.gradle.libraryelements 'resources' and found compatible value 'jar'.
          - Variant 'jvm-runtime' capability io.kotest:kotest-runner-junit5-jvm:4.0.2:
              - Unmatched attributes:
                  - Found org.gradle.status 'release' but wasn't required.
                  - Found org.gradle.usage 'java-runtime' but wasn't required.
                  - Found org.jetbrains.kotlin.platform.type 'jvm' but wasn't required.
              - Compatible attribute:
                  - Required org.gradle.libraryelements 'resources' and found compatible value 'jar'.
          - Variant 'metadata-api' capability io.kotest:kotest-runner-junit5-jvm:4.0.2:
              - Unmatched attributes:
                  - Required org.gradle.libraryelements 'resources' but no value provided.
                  - Found org.gradle.status 'release' but wasn't required.
                  - Found org.gradle.usage 'kotlin-api' but wasn't required.
                  - Found org.jetbrains.kotlin.platform.type 'common' but wasn't required.

Jvm version:

Using java version 13.0.2.hs-adpt

This worked fine with the latest version of

kotlintest

.