Mark, Good ideas.. I went by your suggestion to move ahead. But this is a potential risk (small one I guess). I assumed that the emulator testing would be enough atleast for the android application. Are there cases where the product has worked well on the emulator but worked differently on the actual product ? Siddharth
On Wed, Jul 15, 2009 at 6:51 PM, Mark Murphy <mmur...@commonsware.com>wrote: > > MCON Dev wrote: > > Would it be a bad idea to expect the android > > guys to provide a valid deviceid, simcard number and phone number with > > their emulator. > > They may not be allowed to, depending how the telecommunications > regulations surrounding "deviceid, simcard number and phone number" are > written. And bear in mind that there may be a couple hundred sets of > such regulations, one per country with cellular infrastructure. > > > With options to change country and correspondingly get > > appropriate test bed ? > > I could certainly see having some emulator command-line switches to > allow *you* to put in fake data. > > Besides, you can do this yourself. Just wrap your calls to getDeviceId() > and kin in some class that detects the null values and substitutes in > values read off of an SD card image, or some local file, or a value read > off of the network. In production, you will use the real values; on > emulators, you will use your test data. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > Android Development Wiki: http://wiki.andmob.org > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
