It used to be possible to have subclasses of the various Spec classes, and IntelliJ would "see" the individual tests. It looks like that's no longer the case, though. We have a subclass of FunSpec that we often use (mostly sets defaults our team expects, and adds some helper methods), and using it, IntelliJ doesn't show a run button (green triangle) next to tests, but if I change it to use FunSpec directly they appear. I think back when this worked was before the kotest plugin (somehow it was just using IntelliJ's JUnit support, I guess?). Is using a custom subclass of Spec just not supported, or is this a bug, or am I doing something wrong?

Hey @sam any suggestions on how i can somehow tell kotest intellij plugin to pick up surefire and failsafe maven configs? I noticed when i try running the unit tests it starts running the integration tests as well because it's under the same package name (despite it being organised in two different folders). We're probably doing the wrong thing altogether so what's your suggestions? Maybe Tags?

Anyone has successfully managed to make usage of the kotest gradle plugin https://github.com/kotest/kotest-gradle-plugin to run jvm unit tests in an android kotlin simple project (not android instrumented tests in a device)? I've configured

plugins {
    id("io.kotest") version "0.1.3"
    id("com.android.application")
    kotlin("android")
    kotlin("android.extensions")
}

in my project (single module for now, it's just to experiment with it), but when running

gradle kotest

i get

Could not determine the dependencies of task ':app:kotest'.
> Task with path 'classes' not found in project ':app'.

gradle test

(with java5 runner) works just fine.

Hi - Is there any documentation of how to use the property based functionality (eg. checkAll) with the AnnotationSpec style?

Hi, when I add this :

implementation("io.kotest:kotest-property:4.2.5")

to my commonTest sourceSet, I get this error when I gradle sync : Could not resolve io.kotestkotest property4.2.5. the goal is to add Kotest to my multi-platform common module (commonTest)

Hello, somebody know how can we run Android Instrumented Tests (in androidTest directory) with kotest?

IDEA shows the option to only run previously failed tests, but my tests are progressive/dependent on eachother. Is there a way to disable this / ensure all tests always run?

This message was deleted.

Hi everyone! I am trying to initialise a

BehaviorSpec

. Since I need to perform some actions before the spec is initialised by using a custom Listener, but it doesn’t seem to work. Here’s an example:

class DashboardViewModelTest : BehaviorSpec({
    listeners(
        MyListener
    )

    // [I need a listener (or multiple listeners) to be executed immediately here]

    val myClassUnderTest = MyClassUnderTest(...)

    Given("Something") {...}
    Given("Something else") {...}

    // [And then I need the same listener to de-initialise my stuff here]
})

How can I have something like that? Of course if I create a wrapping Given, for example, the listeners actually get triggered, but I was trying to avoid a further nesting level with something like Given(“My class initialised”), it seems redundant to me.

@sam PR's up 😆 https://github.com/kotest/kotest/pull/1733

Not completely sure if its related to kotest or not, sb suggested to cross-post here. If sb know about this lemme know 👀

Hi @kotest-team, can you tell me why you moved from dokka to javadoc? Asking cuz curiosity and for my projects.

G'day! In IntelliJ, in the project left panel, when I right click on a package and select

Run -> All tests (kotest)

the Kotest plugin runs all the tests defined in that package ignoring the specific directory I am in (in my case src/test/kotlin whereas we have also integration tests in src/it/kotlin). What is the best way for me to create a test suite consisting of only unit tests excluding integration tests?

Is there a way to do "1".shouldBeLessThan("5", myComparator) I can only see that I can use my comparator in equals/notEquals

Hello everyone, I am facing one issue related to test cases. My Android project has more than 250 tests. Most of them include API mocking & some of them are unit tests. In Android Studio when I run the individual test class, all tests in that class succeed. But when I run the entire test package(altogether), some of the tests fail randomly. The project has 

MockWebSerever

 & 

Awaitility

 to handle API mocking & async operation. The 

.gradle

 file also has Android Orchestrator & clearPackageData declared. Still, the issue persists. Can someone help me to fix this issue? My gradle, plugin & java version:

Hi everyone! Сan you tell me how you can set up a kotest to run from a test task? kotest-gradle-plugin is not what I want) "useJUnitPlatform()" - in build.gradle is specified

How do I configure Robolectric tests? Doing this doesn't seem to work:

@Config(sdk = [Build.VERSION_CODES.O_MR1])
@RobolectricTest
class SomeTest : DescribeSpec({ ... })

Hi guys, what do you think about this, it should fail right?

listOf<Int>(1) shouldBe listOf<Int>()

Ok regarding the Robolectric extension, let’s go by small steps. First thing first, I’ve noticed it isn’t generating in the latest versions of the library (the last extension version available in the maven repo is the

4.0.1

). I’ve created a PR to re-include the plugin in the project artefacts generation, unless there was a reason why it wasn’t included anymore (@sam to confirm). The PR is this one, it includes also some further fixes and optimisations in the Gradle file. After that, I will try to reproduce the bugs about Robolectric itself, although from some comments I understand it might be not as immediate to fix them.

Good news, I’ve managed to get a Robolectric test to work with a local updated version of the Kotest Robolectric extension. Work in progress about both Robolectric and Android support for it, I hope to release PRs at a certain point!

Hi there, this is kinda out of left field but something I've been thinking about for a few days and kotest seems like my best bet. I have a set of junit tests that end up spending a lot of time waiting for things using failsafe's retry. Since kotest uses suspend functions (and so do my test methods I'm using for my e2e testing) I was wondering about the feasibility of extending kotest to wrap each test case in a function that returns a deferred test result, something like:

val tests: List<TestCase>
suspend fun executeAsync(testCase: TestCase...): Deferred<TestResult>...
fun doIt() = tests.map { executeAsync(it) }.awaitAll() // or just start them instead

If my failsafe retries were kotlin's

delay

then my other tests would run whatever they can instead of waiting for each test case to complete serially, at least that's the way I understand it.

Any clue?

@alexfacciorusso is working on re-releasing our roboelectric plugin, and we're trying to decide where is best to locate it. So does anyone have any opinions on the following options: 1. release as part of the main project 2. separate repo, same version 3. separate repo, different versioning, with normal module names 4. separate repo, different versioning, kotestx module names

wondering if anyone else is experiencing unusably slow IntelliJ performance, especially in kotest specs (WordSpec in this case)? by slow I mean more than a minute for type completion to pop up … on a machine with i9900k CPU & 64GB RAM (4GB heap for IntelliJ)

How can I store a value which can be accessed in multiple tests? I have several files each containing a StringSpec class with tests in it, and have added a project level config with a beforeAll function in it, which is being called before tests run. I'm currently trying to add a variable in that listener which can then be accessed by any of the tests, but not sure how to do this or what is the best way (I'm quite new to Kotlin). Can anyone help to point me in the right direction please?

does kotest support something like minutest’s fixture? http://oneeyedmen.com/my-new-test-model.html

I'm looking for a way to use the config on FunSpec style, is that possible?

"danger will robinson".config(enabledIf = disableDangerOnWindows) {
  // test here
}

I have an analog to Arrow's

Either

type, and I'd really like to do something like

val actual: <Unit, Errorish> = doThing()

withClue(lazy { "doThing error: ${actual.errorOrNull()?.message}" }) { 
  actual.isOk shouldBe true
}

Is this possible and I'm just not seeing a way in the current matchers? Basically I don't want to try to get the error message unless there's an error in my value