1. Core functionality of the app is working as expected.
2. UI of the app is as expected like all elements are
aligned properly; there is no truncation of element or text etc. UI should be
consistent across all screens of AUT.
3. Touch area of all touchable elements is big enough so
that normal user does not feel any problem in touching them.
4. Font size of all the text should be optimum i.e. neither
too small nor too big so that normal user is able to read it with ease.
5. UI remains consistent on rotating the device. If user is
reading some text then on rotating device text/list should not scroll to top
i.e. it should maintain current position.
6. If on rotating device there is some extra space then
elements should be automatically adjusted accordingly i.e. either size of the
elements should be increased or other elements (for which user was required to
scroll earlier) should be displayed on the screen.
7. Smart phones automatically handle most of the suspend
resume functionality automatically but testers should also test it especially
in case of audio & video play.
8. If AUT is accessing any third party / inbuilt app like
contacts, messaging, email, facebook etc. then it should transfer required data
properly and on coming back to AUT should be smooth and should come back to the
same screen from where user left.
9. If AUT needs to download very large data then it is
recommended to be downloaded asynchronously i.e. initial chunks of data should
be downloaded first and user should be able to read text or scroll list while
rest of the data is being downloaded.
10. If AUT has some authentication screen like login screen
then keep an eye on network log to make sure that AUT does not pass username
& password in plain text. Also after logout such authentication tokens /
session id should be deleted.
11. If AUT is saving some personal information like
authentication token, password, credit card then it should be saved in
encrypted form.
12. Instrumentation should be used to check memory leaks and
memory consumed by AUT during run.
13. App should
support all the orientation of the device. If not, then both variations of the
orientation (in case of portrait mode - upside-down).
14. On uninstalling, all the files related to the AUT
should get deleted and other apps should remain unaffected.
15. If AUT displays badge on the app icon then it should
display correct count and on every update it should be updated accordingly.
16. If AUT has popover then popover should not have any
explicit close button. Instead it should disappear when user taps on any item
on it and corresponding action should take place or user tab anywhere else on
screen.
17. All navigation should be self-explanatory like Back
button should take user to logically previous page, Cancel button should cancel
current operation etc.
18. If AUT has scroll-able form like screen then currently
focused text field should be visible to user i.e. keyboard should not hide it.
And on hiding keyboard screen should be adjusted accordingly.
19. Navigation from one screen to another or screen rotation
should not be abrupt. AUT should animate components smoothly.
20. Switching between Wi-Fi and mobile network should not
affect functionality of AUT. Also if device’s Wi-Fi and network are disabled by
user (i.e. Airplane mode) and AUT tries to make any network call then AUT
should be display appropriate error message to user, asking him to enable
Wi-Fi. In such scenario AUT should not display loading bar before should error
message.
21. Battery consumption should be under control when AUT is
running.
22. One of the most important aspects is performance of the
AUT. AUT should not be very slow otherwise user will move to other similar
apps. AUT should keep user engaged and should display results as quickly as
possible.
23. Testing AUT using different network connectivity like
Wi-Fi, 3G, 2G etc.
24. AUT should handle network failure scenario gracefully
e.g. device loses network while AUT is downloading some content. In such
scenario a proper error message should be displayed after timeout i.e. AUT
should not keep displaying loading screen indefinitely.
25. Special testing should be done to verify how AUT handles
foreign characters and special characters.
26. If new version of AUT is available then user should be
notified about the update and AUT should be updated smoothly without deleting
existing user’s data and preferences.
For more details refer to Apple’s Human Interface
Guidelines.
A very good iOS testing tree could be found here
I wondered upon your blog and wanted to say that I have
ReplyDeletereally enjoyed reading your blog posts. Any way I’ll be
subscribing to your feed and I hope you post again soon.
Mobile App Development Company