DslMarker not propagating properly in IDEA builds test tree incorrectly

[BorzdeG]

kotest: 5.2.1
kotest plugin: 1.1.49-IC-213-EAP-SNAPSHOT
IDEA: 2021.3.2

The test starts through GRADLE run Configuration

sample code:

import io.kotest.core.spec.style.DescribeSpec
import io.kotest.datatest.withData
import io.kotest.matchers.shouldBe

class DemoTest : DescribeSpec() {
	init {
		describe("desc - 0") {
			it("it - 0") {
				withData(
					1 to 1,
					1 to 2
				) { (x, y) ->
					x shouldBe y
				}
			}
		}
	}
}

[sksamuel]

You can only put withData inside containers, so it's binding to the describe level. This is a bug in the sense that you shouldn't be able to create a test like that.

…

On Tue, 15 Mar 2022 at 13:15, Viktor Alenkov ***@***.***> wrote: kotest: 5.2.1 kotest plugin: 1.1.49-IC-213-EAP-SNAPSHOT IDEA: 2021.3.2 sample code: import io.kotest.core.spec.style.DescribeSpecimport io.kotest.datatest.withDataimport io.kotest.matchers.shouldBe class DemoTest : DescribeSpec() { init { describe("desc - 0") { it("it - 0") { withData( 1 to 1, 1 to 2 ) { (x, y) -> x shouldBe y } } } } } [image: image] <https://user-images.githubusercontent.com/2332528/158444640-1fbcd907-38dc-4082-9a44-e563df670052.png> — Reply to this email directly, view it on GitHub <#2878>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFVSGXYCOM3XKR5MSTCGF3VADHUPANCNFSM5QZQIVKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[sksamuel]

This is giving an error in 5.2.1 now.
Can you confirm @BorzdeG

[BorzdeG]

@sksamuel Yes, the error persists. Published a demo project: https://github.com/BorzdeG/bugs-kotest-2878

[sksamuel]

It must be fixed in master because I can't duplicate.

I am going to release 5.2.2 so we can try against that.

[BorzdeG]

Upgrading the versions didn't fix the problem. Updated repository

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[sksamuel]

@BorzdeG I have played with your repo and I don't understand.
The same test in kotest shows the red build. Inside your repo it's green.
The versions are identical and the code is the same.

[BorzdeG]

The problem seems to be in how the test report is generated: build/test-results/test/TEST-demo.DemoTest.xml

<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="demo.DemoTest" tests="3" skipped="0" failures="1" errors="0" timestamp="2022-05-03T05:34:57" hostname="borz-mac.local" time="0.231">
  <properties/>
  <testcase name="(1, 1)" classname="demo.DemoTest" time="0.03"/>
  <testcase name="(1, 2)" classname="demo.DemoTest" time="0.003">
    <failure message="io.kotest.assertions.AssertionFailedError: expected:&lt;2&gt; but was:&lt;1&gt;" type="io.kotest.assertions.AssertionFailedError">io.kotest.assertions.AssertionFailedError: expected:&lt;2&gt; but was:&lt;1&gt;
	CUT_OUT
</failure>
  </testcase>
  <testcase name="it - 0" classname="demo.DemoTest" time="0.635"/>
  <system-out><![CDATA[]]></system-out>
  <system-err><![CDATA[]]></system-err>
</testsuite>

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.