I'm seeing that when I add kotest 4.1.1 as a dep I'm failing to resolve

com.github.ajalt.clikt:clikt:2.6.0

...anyone else seeing that?

I just noticed that

shouldThrow<SomeException>

won't match if a sub-type of

SomeException

is thrown. But when I try and test with code equivalent(?) to what's in

shouldThrow

, it does match. I'm an idiot. Nothing to see here.

I asked a while back but didn’t follow up: what was the reasoning to remove

context

block in

DescribeSpec

? @sam you mentioned (in https://kotlinlang.slack.com/archives/CT0G9SD7Z/p1593192969030900) that now nested describe blocks are allowed, but they were allowed for almost a year, since 3.4 I think. I’m asking primarily since it’s a bit surprising to see such breaking change between 4.0 and 4.1

Unable to run Kotest with Kotlin 1.4-M3 My gradle has the latest Kotest dependencies.

listOf(“runner-junit5”, “assertions-core”, “runner-console”, “property”).forEach {
        testImplementation(“io.kotest:kotest-$it-jvm:latest.integration”)
}

I tried with Intellij kotest plugin-1.0.5 as well and getting the below failure:

Why latest robolectric-extension is

4.0.1

version? Is it compatible with kotest

4.1.+

?

do we have to add any additional dependency to gradle in order to debug test which have coroutines and suspending functions ?

What’s the idiomatic way to make list assertions using matchers? That is, having

List<T>

and a

Matcher<T>

, what’s the best way to check something like

List<T>.shouldContainInOrder(List<Matcher<T>>)

?

1. I’m developing a small change in the Kotest settings to allow controlling the case on tests’ names. How can I force settings values on the tests to test each scenario?

2. I’m using Kotest in another project, and I’m verifying dependencies there, where may I find the public PGP key to validate Kotest’s dependencies integrity?

@LeoColman (and sorry to address you directly) we seem to have a memory problem with

SpringListener

. we are still investigating and cannot confirm yet, but looking at the implementation `TestContextManager`s are stored for each Spec but never removed, so that looks like a candidate. For comparison, junit `SpringExtension`removes the context in an

afterAll

method (which should equivalent to

afterSpec

). do you think we are wasting time or might we be onto something here?

Hey 👋 Is it expected that

beforeTest

of a nested scope is not executed for child scopes when the default isolation mode is chosen? Example:

// beforeTest on the most outer level at the top of the spec
beforeTest { ... }

describe("some scope") {
  beforeTest { ... }

  // for these tests, the outer level and "some scope" beforeTest functions are executed in order before each test
  it("test a") { ... }
  it("test b") { ... }

  describe("some deeper scope") {
    // for all these tests only the top level beforeTest is executed before each one, but the "some scope" one is never executed
    it("test c") { ... }
    it("test d") { ... }
  }
}

When I change to

IsolationMode.InstancePerLeaf

it works, but I don't really need separate instances, I just need the

beforeTests

of each parent to be executed for each test case. If this is a bug, I'm happy to create an issue.

Hi, Just heard a lot of nice things about kotest. Never used it before though. I read about it in the scope of Assertions, but from reading the documentation it sounds like a separate test framework. So is it used instead of Junit5 or together with that?

Is there a way to output test results as Junit XML files, and is the junitxml extension needed for this?

Hi, is it possible to test an abstract class with kotest?

I'm getting complaints about 2

should

blocks having the same text for: "duplicated test name" (even though they are within different parent scopes. i.e.:

"one" {
    "a" {
        should("c") {}
    }
    "b" {
        should("c") {}
    }
}

I had an idea to improve springlistener in some cases where the method name actually matter. https://github.com/kotest/kotest/issues/1591 is it ok? I can work on it (I don’t know when, but it is probably not very urgent), but the question is, does it make sense? probably it needs a flag as well, since only few characters are allowed in method names. Would there be something else to be particular mindful to verify?

Does anybody have some experience working with parallel test execution? Basically we would like to execute multiple specs in parallel to make use of all the cores we have, but we have some test files that do some static mocking, so these files would influence other test files that would run at the same time on a different thread. Is there any way to leverage the tagging system to mark these files to be run sequentially, while all the other tests can make use of parallelism? If not, do you think this might be something worth exploring in the project?

This is an update/repost of prior post on this channel Does anyone know of an example project in Github (or wherever) that successfully uses Kotest in a multiplatform project with IOS and Android as the targets? I have this type of multiplatform project, and can successfully run/debug unit tests using JUnit5 and the basic kotlin.test stuff. But if I add a Kotest class (in this case extending StringSpec) in the same test source directory and in the same package, the IDE shows it as if it should compile fine. Attempting to run or debug the test using the gutter menu fails. For some reason gradle is not compiling the class before the debug run despite a successful build, so the debug attempt fails with a ClassNotFoundException. The build directory "build\tmp\kotlin-classes\debugUnitTest\com\oldguy\io\tests" is where the compiled class should be, but it is not present. Only the unit test class using kotlin.test is present. It is as if the build doesn't realize the Kotest class is a unit test and skips compiling it. This is using 1.4-M3 and Kotest 4.1.2. The test classes are in the top level androidApp module in the src/test tree of this multiplatform project. I haven't been able so far to get unit tests to run in any of the underlying multiplatform modules due to issue https://youtrack.jetbrains.com/issue/KT-40571. Also, if anyone knows a gradle change to get the build to recognize the Kotest class as a unit test and build it, I would appreciate that info as well. Thanks in advance for any info

I've noticed a problem with Kotest run configurations in IntelliJ - the VM options does not save when storing as a project file, and it sometimes loses its content. Has anyone else noticed this?

In fact that 4.1.3 version gives me problems with the Kotest plugin

I'm seeing an issue where if I run a single test, it passes, but when I run all the tests, a test fails. I do modify the values of some global variables in the tests (unavoidable, unfortunately), but I run them single threaded and in order. A test set a var at the top of a

should

block, and then resets it at the end, so I thought I'd be covered?

Whenever a single test fails, gradle (or kotest?) reports two failures. It seems like once there is a failure, "doubles up" as

executionError

as if that was an additional failing test. Any idea why? (2 actually failing tests gets reported as 3 failures)

Is there a way to add information to the assertion failures? For example if I do something like

errorOccurred shouldBe false

or

errorOccurred.shouldBe(false)

then the assertion failure says something like

expected:<false> but was:<true>

Is it possible to add more information to make the problem more clear? If it could display the name of the variable being checked that might be enough.

Config is 1.4.0-rc and the 1.1.0 kotest plugin, and using kotest 4.2.0 snapshot in Android Studio in a multi platform project. if I use the gutter menu to debug a test in a multiplatform module, and the gradle debug build task ":<<moduleName>>:assemble" fails with errors, the debugger is still invoked. Is this a Kotest plugin thing, or a defect elsewhere?

Upgrading a repo from kotlintest to kotest, is it possible to do property testing with just a specific set of values? (like kotlintest had)

Config is

4.2.0.426-SNAPSHOT

and the 1.1.0 snapshot of the Intellij plugin in Android Studio. Make a unit test using the AnnotationSpec setup.  It looks fine in Android Studio, and gradle compiles it fine, but there is no gutter icon on this style of test in my multiplatform module set of tests.  Other tests in the same module using StringSpec work fine.  Anyone else seen this issue with AnnotationSpec? FYI manually creating a Run configuration for the same unit test class lets runs/debugs work fine.

In kotlintest I was able to add arbitrary metadata via the

testContext

member in a

ShouldScope

, does something equivalent exist in kotest?

why is there no plusorMinus() for Long? there is one for Double and Float https://github.com/kotest/kotest/blob/f329f592ce3b285c5d8f1c255098b233e74f477d/kotest-assertions/kotest-assertions-core/src/commonMain/kotlin/io/kotest/matchers/floats/FloatMatchers.kt#L7

I'm still seeing

[ERROR] Failed to execute goal on project jicoco-test-kotlin: Could not resolve dependencies for project org.jitsi:jicoco-test-kotlin:jar:1.1-SNAPSHOT: The following artifacts could not be resolved: com.github.ajalt.clikt:clikt:jar:2.6.0, com.github.ajalt.clikt:clikt-js:jar:2.6.0, com.github.ajalt.clikt:clikt-linuxx64:klib:2.6.0, com.github.ajalt.clikt:clikt-metadata:jar:2.6.0: Could not find artifact com.github.ajalt.clikt:clikt:jar:2.6.0 in jitsi-maven-repository-releases (<https://github.com/jitsi/jitsi-maven-repository/raw/master/releases/>) -> [Help 1]

when I include the

kotest-runner-console-jvm

in my pom and try to compile from the command line. @sam I think you said the need for this dep is going to go away soon (because it will be bundled). Is that right? Has that been released?