IPhone iPhone Testing Best Practice

Question

Not so long ago, iPhone development was quite simple, with only a few versions of the OS and even fewer devices.

Now, however, there are 2 major versions of the OS and 5 different devices.

As a company released to test multiple applications, it has become more and more a problem.

What are the best ways to test all combinations, do I need to purchase every generation of iPhone and iPod Touch? Are there any bugs with specific hardware / OS combinations that I might need for the code?

I think my question is: "What is the minimum amount of testing that should cover all databases?"

Answer 1

, iPod/iPhone. , :

• . iPhone v1 iPhone 3G 412 ; iPod Touch 532 , 3GS 600 . , .
• EDGE/3G/WiFi; . EDGE ( ), 3G, 3G 10- . .
• Core Location? iPhone v1 iPod Touch GPS.
• ? iPod Touch .
• jailbroken-? , , , Dev Team, App Store. , , , , . .

, ? , , 5 . 5 ? 5 ? .

, , , iPhone 3G iPod Touch. 3GS, , , . ( , 3GS , , ).

, 3G iPod- (, , 3GS).

Answer 2

iPhone, . 90% . , , gotchas, .

Answer 3

, . , ibetatest , . - .   95% , , - ibetatest 5%.

Answer 4

- .

iPod, 100 , iPhone. , iPhone. - (?) GL.

Answer 5

:

• , , . , iPod Touch/iPhone .

• You may want to explore the use of crowd sources to complement your internal testing. This potentially allows you to have a large audience to test your applications, and any costs for using crowd sources are potentially offset by the fact that you can spend less on devices and possibly less on internal testing staff and at the same time potentially better product. One test group not listed above is uTest.com