Adarsh Ramamurthy

That's odd but there is nothing different about the way the plugin is published. Have you tried running with info or debug log level turned on to perhaps get some...

The exception you are seeing is mostly as a result of https://github.com/radarsh/gradle-test-logger-plugin/issues/241#issuecomment-1060628271. There is nothing that can be done about that if you are using Gradle < 7 and plugin...

I think one set of outputs is from Gradle. Do you have Gradle's `testLogging` configured as well?

Can you try setting this in your build script and let me know if that fixes things? ```diff test { testLogging { + showStandardStreams = false } } ``` Up...

Thanks, that was useful. Can I ask you to try setting this as well please? ```diff test { testLogging { + lifecycle.events = [] } } ``` If this setting...

This already happens if you use one of the parallel themes. Is this not what you're after? 

I've been thinking of an idea to print the top-5 or top-n slow tests across the whole project. This along with a few other metrics could form a statistics summary.

Thanks for clarifying that. Yes, it was an annoyance to convert from JSON to JS eslintrc but at least it was a one-off.

You can always modify your tags configuration to look like this to support picking up runtime tags. ```groovy cucumber { tags = System.getProperty('tags').split(',') } ``` Then you can supply one...

@Ravinderkaur04 if you don't pass any system property called `tags`, that code won't work. You can use this null-safe variation to make sure it works regardless of the system property...