Adam Monsen wrote:
>
> After a successful build, "gradle test" or "gradle build" just says
> everything is "UP-TO-DATE". Is this expected?
>
Yes, it is expected. As a long-time Maven user, it keeps surprising me
though.
"UP-TO-DATE" means that a task's inputs and outputs haven't changed since
the previous run. For the test task, the inputs are (roughly speaking) the
test classes and the test class path (I guess the latter includes the
classes under test), and the outputs are the test results (XML files) and
test reports.
Adam Monsen wrote:
>
> Is there some way to force that?
>
"gradle cleanTest test" is the best I've found. You could turn this into its
own task like so:
task "forceTest" {
dependsOn "cleanTest", "test"
}
Cheers,
Peter
--
View this message in context:
http://gradle.1045684.n5.nabble.com/how-does-gradle-decide-when-to-run-tests-tp3314172p3314397.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
