On 23/12/2010, at 4:45 PM, Luke Daley wrote: > > On 23/12/2010, at 3:43 PM, Adam Murdoch wrote: > >> >> On 22/12/2010, at 8:56 AM, Adam Monsen wrote: >> >>> After a successful build, "gradle test" or "gradle build" just says >>> everything is "UP-TO-DATE". Is this expected? >>> >>> Here's my build file: http://tinyurl.com/2dvlcpv >>> >>> I think I'd rather that tests ran every time I do "gradle test", even if >>> nothing changed. Is there some way to force that? >> >> I'm curious why you would want to run the tests even if nothing has changed? > > Sometimes there are external factors.
I guess I was after something a bit more concrete. I suspect there are some things here we can model, to make better decisions about whether to run tests (and, ideally, which ones to run). > Changes to the build script also don't seem to count as a change here. If you make a change that affects how the test task is configured, then the task will be considered out-of-date. This includes things such as changing dependencies, include/exclude patterns, or whether junit or testng is used. However, it looks like I missed a few annotations, so it doesn't consider test system properties, environment variables, and a couple of other things. I'll fix these for 0.9.1 -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
