I added a bounty to this StackOverflow question from a couple of months
ago:

http://stackoverflow.com/questions/20137033/can-gradle-tests-live-peacefully-with-old-style-test-projects

In short, is there a recipe for a project structure and build.gradle
file that would allow instrumentation tests to be run from Eclipse/Ant
*and* from Gradle? Since Gradle wants the test code to be a sourceset,
and Eclipse/Ant want it to be a project, I'm stumped as to how would
would accomplish this (except perhaps via some symlink games, which then
can cause version control issues).

If it helps, my particular area of interest is in testing an Android
library project, but a more general-purpose solution certainly would be
welcome.

Thanks!

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_: Version 5.5... And
Still Going Strong!

-- 
You received this message because you are subscribed to the Google Groups 
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to