marcingrzejszczak / gradle-test-profiler

created with @AChudzik. The idea of this plugin is to perform profiling of your tests. You will be able to see your test execution times sorted in the descending manner together with an information about a module and the class name from which the test was executed.
Apache License 2.0
25 stars 11 forks source link

Plugin logs report generated message even when profileTests task is not used #41

Closed mattfirtion closed 5 years ago

mattfirtion commented 8 years ago

Gradle will output that a test report is ready, even though profileTests task was not called.

marcingrzejszczak commented 8 years ago

Could you please show me your configuration of build.gradle ?

mattfirtion commented 8 years ago
apply plugin: 'java'

buildscript {
    repositories {
        mavenCentral()
        jcenter()
    }
    dependencies {
        classpath 'com.blogspot.toomuchcoding:gradle-test-profiler:0.3.1'
    }
}

apply plugin: 'com.blogspot.toomuchcoding.testprofiler'

repositories {
    mavenCentral()
}

dependencies {
    testCompile 'junit:junit:4.8.2'
}

testprofiler {  
    String separator = "|"
}

Exec: gradle clean build

marcingrzejszczak commented 8 years ago

@achudzik - can you address this issue?

marcingrzejszczak commented 8 years ago

I think I know why ;)

By default reports are always created. The profileTests is combining the generated tests into one.

The default behaviour is such that test listener is automatically applied when you're applying the plugin. The test listener's behaviour results in creation of reports. You would have to disable the feature with the extension.

marcingrzejszczak commented 8 years ago

@mattfirtion - can we close it?

marcingrzejszczak commented 8 years ago

@mattfirtion ping? :)

marcingrzejszczak commented 7 years ago

super ping? :P