Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test name printing on console running gradle is cryptic #6

Closed
arturbosch opened this issue Nov 3, 2018 · 3 comments
Closed

Test name printing on console running gradle is cryptic #6

arturbosch opened this issue Nov 3, 2018 · 3 comments

Comments

@arturbosch
Copy link

Hey, thanks for the library.

When running gradle test the name of the tests is not the same as specified in the testcases.
It is just tests()[number]

Please see the output:

io.gitlab.arturbosch.afk.uast.visit.TraversingSpec > allows to traverse back to UFile PASSED
io.gitlab.arturbosch.afk.uast.visit.UastRegistrarSpec > Given: registered UFile visit event PASSED
io.gitlab.arturbosch.afk.uast.visit.UastRegistrarSpec > When: two different lang UFiles are visited PASSED
io.gitlab.arturbosch.afk.uast.visit.UastRegistrarSpec > Then: the event counter must be two PASSED
io.gitlab.arturbosch.afk.uast.visit.UastVisitorSpec > prints names PASSED
io.gitlab.arturbosch.afk.uast.visit.TraversingTest > tests()[1] PASSED
io.gitlab.arturbosch.afk.uast.visit.TraversingTest > tests()[2] PASSED
io.gitlab.arturbosch.afk.uast.KotlinParsingSpec > tests()[1] PASSED
io.gitlab.arturbosch.afk.uast.KotlinParsingSpec > tests()[2] PASSED

The first four tests are written using spek2 and the last four minutest.

Gradle is 4.10.2, Kotlin 1.3, Junit 5.3.1, Junit-Platform 1.3.1, minutest 0.20.0, strikt 0.16.4

greetings.

@npryce
Copy link
Collaborator

npryce commented Nov 5, 2018

This appears to be a bug in Gradle: gradle/gradle#5975

@dmcg
Copy link
Owner

dmcg commented Nov 5, 2018

I think that Spek has its own runner, which might explain how it doesn't suffer.

@dmcg
Copy link
Owner

dmcg commented Nov 6, 2018

I'm going to leave this open for reference although it isn't clear what we can do about it, short of fixing Gradle. Which might be an option. I mean, how hard can it be?

dmcg pushed a commit that referenced this issue Nov 11, 2019
@dmcg dmcg closed this as completed Nov 11, 2019
dmcg pushed a commit that referenced this issue Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants