Hello, Sarcasm is not necessary. Just try to imagine, that devs have changed a very big application's design a bit to use separate processes and as a result you have lost almost 4 human years of work. All UI tests. And all Continious Integration servers became useless, because there are no tests to run anymore.
I would love to laugh with you on my problem after we find the solution, but now there are nothing to laugh on.. Best regards, Yahor On Tue, Jan 31, 2012 at 3:43 PM, Mark Murphy <mmur...@commonsware.com>wrote: > On Tue, Jan 31, 2012 at 8:36 AM, Yahor Paulavets > <ypaulav...@agilefusion.com> wrote: > > It is not my app, it is app I have to test. And it is not testable, > because > > it has ":separate" processes. > > Ah, my apologies. Please direct my rants to the developers, who should > have their heads examined. > > > I wonder to know, is there are any way to test such processes? > > I doubt it, at least in terms of ActivityInstrumentationTestCase2 and > kin. Android does some magic to load your test cases into the same > process as the main app; I'll be rather surprised if they can somehow > magically extend that to other processes and coordinate between them. > > Or, to look at it another way, if Diego Torres Milano did not have a > solution for you, then it is likely that no such solution exists -- > he's probably the world's leading expert on this subject. > > You could try monkeyrunner, as that has a chance of handling multiple > processes. > > > Or how can I submit a bug/ask google/whatever to get the answer or > > direction.. > > You are welcome to file a feature request at http://b.android.com. > That will not help you in the short term. > > > update: if I remove ":process" separate process definition in the > manifest file, application crashes and there are no way to run it without > separate process definition. > > That is because the developers wrote a lousy app. If monkeyrunner does > not fit your needs, report back to whoever assigned this app to you > that the app is untestable in its current state, and that the > developers should remove the android:process attributes and fix their > app. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.7 Available! > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
