Hi all, If this is not the place, you can tell and...

# kotest

[tieskedh]

Hi all,
If this is not the place, you can tell and I will remove my question.
In the past I saw a video about testing, where they isolated the path that only the failing test touched.
By isolating that path, it should be easier to view which code is incorrect.
At this moment, I can't find any information about this.
Does anyone have more information about this, such as a name, or even better, where I can find how to do this?

[sam]

What do you mean by isolating the path - do you mean just running a single test ?

[tieskedh]

I mean cross-reference the passed tests with the failing one.
(A passing test biases the code it crosses towards correct, the more passing tests cross a particular block of code, the more likely it is to be correct)
Although the easiest variant is just looking to places that only the failing test crosses and none of the other test

[sam]

Oh I see what you mean, a bit like code coverage. This isn't something kotest does.

[tieskedh]

Haha, thx.
I think this wasn't entirely correct of me to post it here.
I posted it here, because this is (to my knowledge) the best testing-framework for Kotlin.
Therefor, the change that someone in this topic knew the answer was the biggest...

[Matteo Mirk]

Do we have any clue as how is this technique called?

[tieskedh]

No, I only remembered a talk on this, that's why I couldn't find more info...
I only know I saw it on a talk a long while ago...
But I think the chance of finding a working method is pretty low or it's not working that well, as otherwise it would probably be wide spread.

[Matteo Mirk]

It’s really a pity, seems very interesting