Allure gradle plugin causes execution of additonal test sets as part of build task about allure-gradle

[NielsDoucet]

We have noticed the same behaviour, where tests are being run when requesting the assemble task.
After discussing with @vlsi on the gradle community slack, it appears this is related to gradle/gradle#6875, as allure results are attached to the build as an artifact.

@benjamindibonasonos Could you verify that you also see those tests executed if you run ./gradlew assemble?

[vlsi]

If you need to configure allure for certain tasks only, I would suggest the following:

allure {
    adapter {
        // Disable automatic configuration
        autoconfigure.set(false)

        // Gather report data from test task only
        gatherResultsFrom(tasks.test)
        addAspectjTo(tasks.test)
    }
}

However, it might be worth adding a slightly better DSL instead of gatherResultsFrom and addAspectjTo .

[benjamindibonasonos]

We have noticed the same behaviour, where tests are being run when requesting the assemble task. After discussing with @vlsi on the gradle community slack, it appears this is related to gradle/gradle#6875, as allure results are attached to the build as an artifact.

@benjamindibonasonos Could you verify that you also see those tests executed if you run ./gradlew assemble?

@NielsDoucet I can confirm that these tests are executed with the "assemble" task.

./gradlew assemble --console=plain                                                                                              
> Task :bootBuildInfo
> Task :compileJava UP-TO-DATE
> Task :processResources
> Task :classes
> Task :bootJarMainClassName
> Task :bootJar
> Task :compileFunctionalTestJava
> Task :processFunctionalTestResources UP-TO-DATE
> Task :functionalTestClasses
> Task :functionalTest