I have about 400 unit tests that I wrote for my Android application. If I run the test package by package, everything works fine, and all my tests pass. However, if I try to run them all at once, eventually (about 360 tests), Android will spit out !!! Failed Binder Transaction Errors !!!. After about 10-20 of these errors, the process for the application that I am testing is killed, and unit tests never complete.
It should be noted that during this time Eclipse reports Collecting test informationin the console. I think this is strange because it shows that it runs tests, although the JUnit interface does not reflect this. When everything works correctly, during the phase Collecting test informationI see that the tests are being executed, then the JUnit UI appears, and then all the tests are started again (I know this by reading logcat). This is (I think) a separate issue, but I felt that I would say this if someone knew what that meant.
Change from June 6, 2011
As with Christopher below, I checked that this only happens when trying to run it through Eclipse. If I run my test suite using ANT, all tests will finally be executed.
When I try to run my test suite, Eclipse essentially freezes up "collecting test information." I do not allow this to work for a long period of time, but I will give it a try as soon as I can to make sure that it will someday end.
source
share