Spek: Improve grouping in JUnit test reports

[madhead]

I've setup a test repo for this issue here.

When I run Spek suites in IntelliJ IDEA, the reports looks awesome:

Suite class's name is visible alongside with it's package. The sings are aligned in tree. Just great.

But when I run tests in Gradle (./gradlew test) the report (build/reports/tests/index.html) is not so good:

• Everything is put inside default-package, which is not true.
• given / describe / on blocks appear in one list.

I understand that reports are not supposed to support custom tree structures, but wouldn't it be better if describe goes to package name and all ons being grouped by them?

Also, XML reports should be tweaked too to improve reporting on CI...

[upelsin]

Any plans for this?

[georgepapas]

bump...
+1

[raniejade]

We just upgraded to JUnit 5 which should fix the XML reports. However currently it doesn't generate the html reports. We will be releasing 1.0 soon, so stay tuned.

[upelsin]

As of Spek 1.0.89, tests still reside in default-package.

[ubuntudroid]

As we're stuck with Junit4 on Android I'd like to know whether you're planning on improving grouping there as well.

[artem-zinnatullin]

@ubuntudroid we're not stuck with JUnit4 "on Android", if you run tests on JVM, you can use JUnit5 (with few hacks for now, but still possible)!

[ubuntudroid]

@artem-zinnatullin AFAIK there is no official JUnit 4 support in the Android Gradle Plugin.

But if it's possible without breaking Android Studio's unit testing capabilities this would be a great thing. Spek's own documentation just mentions Junit4 support for Android. Would you mind updating it? https://github.com/JetBrains/spek/blob/master/documentation/src/asciidoc/setting-up.adoc#setting-up-legacy

[y0sh33]

bump +1

[grine4ka]

Do I understand correctly that this issue is blocked by some issues in gradle?
Like these:
#4438
#4252

[jcornaz]

Will this issue be solved for Spek 2.0.0?

Loosing hierarchy information in reports make it very cumbersome to track the cause of failing tests.

@grine4ka I don't see how it could be related. Theses are gradle issue. Spek shall produce good test reports independently on the build system used. No matter if it is gradle, maven or something else.

[raniejade]

@grine4ka is correct as we depend on gradle for generating reports. Spek already reports the proper hierarchy , it's all up to gradle on how it is rendered.

[jcornaz]

Thanks @raniejade for the precision. Does it mean that maven users don't experience this issue?

[raniejade]

I'm not sure, I don't use maven that much.

[jcornaz]

I'm not sure, I don't use maven that much.

I experienced the same with Maven.

Spek already reports the proper hierarchy , it's all up to gradle on how it is rendered.

Should this issue be closed then?

Or maybe Spek could provide a workaround? By concatenating the hierarchy information in the test name for instance.

[raniejade]

Or maybe Spek could provide a workaround? By concatenating the hierarchy information in the test name for instance.

Nope, hacky solutions will only add more problems.