Leonardo Colman Lopes

Closed as per #3876

We'll probably have to find a new way to do it, similar to what we've done with previous JVM deprecations Thanks @moddyfire !

Only when running individual tests? When running, for example, the entire "SampleTest", do all tests behave as expected?

Closed as duplicate of #3651

I think what you're looking for here is [Soft Assertions](https://kotest.io/docs/assertions/soft-assertions.html) Your example would be converted to ``` val myMap = mapOf("a" to 1, "b" to 2) assertSoftly(myMap) { it shouldNotContainKey...

What platform are you trying to run this test in? Nothing seems wrong with it to me, as far as I can see

I'd say it makes sense to have this kind of matcher. It doesn't seem to be easy to implement and test 😅 Improving the existing `shouldContainExactlyInAnyOrder` seems the best approach...

And the way you are displaying fields it seems that you'll be using reflection for that. If this matcher is not for JVM only, I don't know how you could...

So do you think we should just document it as such @OSemenovBoyarka? As I understand, you made it work with a simple change to the definition, right?

This seems to be easily changeable to ```kotlin fun describeInteg( name: String, enabledIf: EnabledIf = { integrationTestEnabled() }, test: suspend DescribeSpecContainerScope.() -> Unit ) = this.describe(name).config(enabledIf = enabledIf) { test()...