I'm not sure if it is, but on this thread it is stated that the Roboelectric tests should go in src/androidTest directory, but the example shows a Roboelectric-test under src/test? Also, when I put the roboelectric test under /test/java it does not seem to be compiled when executing the 'test' command from sbt, while it does (attempt) to compile the test when I place it under src/androidTest/java (but fails with 'class not found' errors on junit types). … or am I missing something?
On Monday, December 29, 2014 11:35:30 PM UTC+1, pfn wrote: > > Why would it be out of date? > > On Mon Dec 29 2014 at 2:34:48 PM Driak <ko...@bitmetric.be <javascript:>> > wrote: > >> Hi, >> >> I'm very curious if anybody has found a solution to running Roboelectric >> tests from SBT, I love using SBT with android and would hate to have to >> drop back to Gradle for this. >> >> I don't know if it has any bearing on this issue, but I noticed people >> are having the same type of classpath issues with roboelectric tests in >> other build environments because the android.jar lib also contains junit >> classes which are incompatible with the junit classes roboelectric >> requires. On these environments the issue can be solved by making sure the >> junit4 lib is on the class path *before* the android lib. >> Is there any way to enforce the junit4 lib to be loaded before the >> android lib with the plugin? (again, not sure this would help but may at >> least exclude this as a possible problem) >> >> (The roboelectric test example project at >> https://github.com/pfn/android-sdk-plugin/tree/master/sbt-test/android-sdk-plugin/robo-junit-test >> >> seems to suggest the roboelectric test should be on src/test/java, not on >> src/androidTest/java… but I guess this example is out of date) >> >> Thnx! >> >> >> On Thursday, October 16, 2014 5:40:39 PM UTC+2, David Pérez wrote: >>> >>> When I started Android + Scala development, I first tried to use SBT + >>> android-sdk-plugin, and I was able to run Robolectric tests. But I don't >>> remember how. >>> >>> Then I switched to Gradle, and I was able to run the tests, but had to >>> change the file layout. >>> >>> Now, I switched back to SBT, and my tests don't run, due to the >>> classpath problem. >>> There must be some trick. >>> >>> Maybe I can create a satellite regular project, that doesn't use >>> android-sdk-plugin. >>> It'll be my next approach. >>> >>> Am Donnerstag, 16. Oktober 2014 01:23:04 UTC+2 schrieb pfn: >>>> >>>> Well, right now, the plugin forces all tests to go into androidTest, >>>> 'test' and 'android:test' both run out of that directory, the difference >>>> is >>>> behavior, the latter treats it as an instrumented test run, the former >>>> just >>>> runs normal jvm tests. >>>> >>>> The hard part is getting all the robolectric stuff to be seen, etc. >>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "scala-on-android" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to scala-on-andro...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to scala-on-android+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
