kotlinlang #kotest

Is there way in kotest to mark test as flaky test so that based on some configuration either kotest will be able to retry that test for given number of time or ignore that test failure with some message. Some flaky test i am able to handle with

eventually

but still some within some integration test some action takes much time that even

eventually

block fails in those scenario it would be helpful to not fail whole build and just warn and continue.

sam

10/07/2021, 11:00 AM

we have repeat but it requires it to pass all times

sam

10/07/2021, 11:00 AM

perhaps we open a ticket for flakyFail=true at which point a fail isn't a flag but a warn

LeoColman

10/07/2021, 12:54 PM

We did talk about this before, having fluid ways to write tests

LeoColman

10/07/2021, 12:54 PM

We had talked about

repeat

retry

, something with

timeout

LeoColman

10/07/2021, 12:54 PM

I don't remember if we created a ticket for that tho

Jim

10/07/2021, 8:49 PM

EventuallyBuilder

has a configurable duration, what’s the difference between kotest re-running and just increasing your duration?

LeoColman

10/23/2021, 6:09 PM

Do we use karma?

dave08

10/25/2021, 10:27 AM

And no nice color output.

dave08

10/25/2021, 2:48 PM

Is this normal at the end of the output:

Copy code

> Task :api:kotest FAILED

FAILURE: Build failed with an exception.

and at the beginning:

Copy code

1.  ApiTest

is empty... there are failing tests, but in another module...

dave08

10/25/2021, 2:48 PM

And again, it doesn't seem to be running all the tests from all the modules...

dave08

10/25/2021, 2:49 PM

(with the kotest plugin)

Sandymcp

10/25/2021, 3:11 PM

Hi I am trying to set up a datatest using 5.0.0.m3. However Intellij is not finding

withData

Sandymcp

10/25/2021, 3:12 PM

Copy code

<dependency>
            <groupId>io.kotest</groupId>
            <artifactId>kotest-runner-junit5-jvm</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>io.kotest</groupId>
            <artifactId>kotest-assertions-core-jvm</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>io.kotest</groupId>
            <artifactId>kotest-framework-datatest</artifactId>
            <scope>test</scope>
        </dependency>

Sandymcp

10/25/2021, 3:13 PM

The version is set in the dependencyManagement of the parent POM

dave08

11/02/2021, 2:55 PM

Wasn't 5.0.0.M4 supposed to be out yet? In the docs the tag is holding by M3...

dave08

11/02/2021, 2:55 PM

And when is 5.0.0 stable planned for?

sam

11/02/2021, 3:05 PM

5.0 will be once 1.6 is released

dave08

11/02/2021, 3:19 PM

And M4? It was supposed to fix a little problem I had to go back to 4.x.x for...

dave08

11/02/2021, 3:19 PM

Also, are listeners deprecated in 5.0.0?

dave08

11/02/2021, 3:19 PM

I was trying to find something about that in the docs...?

dave08

11/02/2021, 3:20 PM

I think I saw something briefly mentioned in the changelog...

sam

11/02/2021, 3:21 PM

Which listener?

dave08

11/02/2021, 3:21 PM

It says: • The

listeners

method to add listeners to a Spec has been deprecated. When adding listeners to specs directly, you should now prefer

fun extensions()

rather than

fun listeners()

. in the changelog...

sam

11/02/2021, 3:22 PM

The listeners method inside the spec is deprecated but not listeners themselves. Listeners and extensions are the same thing.

dave08

11/02/2021, 3:24 PM

But in 4.x you can't pass a TestListener to

extension(...)

...

dave08

11/07/2021, 2:14 PM

Does the kotest gradle plugin put out:

Copy code

▼ Expect that CustomerFound(customerId=111):
Expected :class ports.input.InitializeAccountResponse$NoOrderDetails
Actual   :class ports.input.InitializeAccountResponse$CustomerFound
<Click to see difference>

it seems like I'm getting a double output on test failure (in Intellij), one like the previous and the other is what Strikt outputs...

Peter

11/15/2021, 3:24 AM

x().shouldBeSome() shouldBe "y"

works ✅