• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Apps How many testing devices do we need?

hiro4476

Newbie
Good day, people!


hope this is the right place to post :)

http://androidforums.com/applicatio...skmanager-fullscreen-support-recent-apps.html
I've got an error that I cannot replicate and debug.
The problem lies in an auth class that I took mostly from Google's example.

People seem to get a "Faild to sign into google" message when they went to "Toggle Items" setting.

But... it's working all fine on my phone!
Was tested on my DHD 2.3.4 (rooted).
Then upgraded to DHD 4.0.4 and tried using different accounts.
Nothing's happened.
All I can do is to wait for people to tell me what's going on.
no fun, no fun at all. And I felt sorry to my users.

Although I might not be able to buy'em all just yet, but I'd still like to know,
What phones /devices do you need in order to do a decent debugging before release?

do you choose the phone by brand? OS version? root or unroot?


Regards,
 
It's impossible to test on every android device, so you need to decide on some minimum requirements, such as Android 2.3+, a set of architectures, etc... Once you have these requirements, you can find a list of devices that fit these requirements. Within this list, try to find devices that are similar. for each set of similar devices, choose one device from it (probably the cheapest :P) and whatever devices you end up with is your ideal testing environment.
 
It's impossible to test on every android device, so you need to decide on some minimum requirements, such as Android 2.3+, a set of architectures, etc... Once you have these requirements, you can find a list of devices that fit these requirements. Within this list, try to find devices that are similar. for each set of similar devices, choose one device from it (probably the cheapest :P) and whatever devices you end up with is your ideal testing environment.

Good day, jonbonazza!

Thanks for the reply!

I learned something in the past 2 days.
1. though you are supporting old devices, use the newest SDK
2. once you switch to a newer SDK, many deprecated methods will rise, deal with'em.

I had my HTC Desire HD upgraded from 2.3.4 Gingerbread to 4.0.4 ICS.
Oddly, the deprecated methods/functions are still working.
For best compatibility possible, maybe someone decided to include the full library inside the phone? :confused:

so, the 3rd point I'd going to add is
3. use Nexus

I assume Google will strip out those deprecated methods?

Now that I've checked my code line by line and had updated my library. Hopefully this will solve the problem :p
 
It's best not to use deprecated methods and classes. They are deprecated for a reason. It's best to use the sdk version that matches your minimum supported SDK and then set your target SDK to the version that you best support. We generally leave the max sdk out of the equation entirely and attempt to support the most current sdk at all times.
 
While the use of a deprecated method is discouraged, it is still a working method. Marking a method as deprecated has the meaning of sending an alert to the developers to stop using it. The reason could be that there is now a better alternative, there is a problem with the implementation or something else. There is also high chance that a deprecated method will be completely removed in the next release.
 
Back
Top Bottom