Is this the same problem you reported in another message? Could you describe the evidence that suggests that something is "freezing"? Does the test package stop producing output? Have you tried this both in Eclipse and from the command line?
I'm not sure why you say that the android test framework is "not stable". There may be a bug in it, but the code for it has been around for a relatively long time. I don't recall anyone else reporting a similar problem. Also, it would help if you posted what version of the SDK you're using. A brief description of your Activity and your tests would also help. If this happened to me, the first think I'd do is write two incredibly simple activity test cases, put them into one test package, and run them against the Activity in question to see what happens. It could be that your Activity is crashing somehow. For an example of a very simple test case, see NotePadActivityTest.java in the NotePad sample app. On Mar 2, 6:05 pm, Mooncheol Yang <[email protected]> wrote: > Hi All > > I wrote test codes(Instrumentation Test of Activities ) and executed.. > > it works well.. but sometimes it's freezing > > so, I checked testcodes, i finally made conclusions that android test > framework is not stable. > > test is executing setup() -> myTestCode() -> teardown() > > i found after teardown() is finished and freezing is occurred. > > Anyone like me same situation? -- 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
