title: Large amount of unit tests cause freezes with Failed Binder Transaction
body: <p>I have about 400 unit tests that I have written for my Android application. If I run the tests 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 in), Android starts spitting out <code>!!! Failed Binder Transaction Errors !!!</code>. After about 10-20 of these errors, the process for the application I am testing gets killed and the unit tests never even complete. </p>
  
  <p>I should note that during this time Eclipse reports <code>Collecting test information</code> in the Console. I think that is odd because it shows that it is running tests even though the JUnit UI doesn't reflect that. When everything works properly, during the <code>Collecting test information</code> phase I see the tests run, the JUnit UI then comes up, and then all the tests are run again (I know this by reading logcat). That is (I think) a separate issue, but I felt I would mention it if anybody knew what that was about. </p>
  
  <p><strong>Edit as of June 6th 2011</strong></p>
  
  <p>As per Christopher's answer below, I have verified that this only happens when attempting to run this through Eclipse. If i run my test suite using ANT, all the tests finally execute. </p>
  
  <p>When I attempt to run my test suite now, Eclipse essentially hangs on "collecting test information". I haven't let it run for an extended period of time, but I will give that a try as soon as I can to see if it ever completes. </p>