Certainly testPreConditions() should be executed. Which version of the SDK are you using?
As for the Activity not being "finished", I'm not sure what Android does in response to mActivity.finish(). I can't really understand what you mean in the second paragraph after the code snippet. Seems like you use debug to change the values from the ones that were set by the test, and you verify that you can see these values in testStateDestroy(). Remember that you're testing the Activity outside of its normal operation. I wonder if you *would* see the spinner on the screen, even if the Activity is running. I wouldn't assume that System.gc() does anything useful. The description of the method is "Indicates to the virtual machine that it would be a good time to run the garbage collector." Not clear to me that the garbage collector is what Android uses at the thread/process level, nor is it clear to me that Android is inclined to GC apps unless there's severe memory pressure. From all I can see, Android wants to keep stuff around if it can. Android developers have to learn to "let go", and trust that they can leave their app "running". -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
