1. Vodafone 360 widget QA Guidelines for developers By Mobica

3. Problems and most commonreasons of rejections

4. A scope of testing

5. How to pass the QA process? – Tips for developers

8. It is difficult to touch interactive elements, such as buttons or links, because they aretoo small;

9. The graphical elements including fonts size, images are too small for comfortable using and reading;

10. Graphical errors on an icon – low quality;

11. If an action takes more than 2 seconds the loading bar is not displayed;Wastingdevelopers’ time to fixsimpleproblems

13. Navigation

14. Extendedmode/Dockedmode

15. Contentstandards

16. APIsbehavior

17. System resources: data traffic, memoryconsumption, batteryusage

18. Update

20. Widgetinstalls successfully;

21. Widget launchesand closescorrectlywithout crashingor freezing;

22. Widgetdoesn`trun any functions of the phone without clear visibility anduser`s permission;

23. Widget’sicon– not a standard deviceicon, sufficientquality, icon image doesn`tcontain theapp`s name;

24. Thenameinsidethewidget and on theiconmust be thesame;Widget execution

26. Widget respondsto dynamic changes in phone orientation;

27. Widgetin fullscreen mode makes use of loading indicators for actionswhich take longer than 2 seconds;

28. Navigation works correctly using the input methods supported by the device;

29. The widget for a touch device usestouch interaction to navigate all functions/screens, e.g. tapping buttons, moving lists up and down- theyrespond to touch interaction on first use, itiseasy to touchthem;Navigation

32. Lunching or closing API doesn`tcrashorclosethewidget;

33. SupportedAPIs: GPS, audio/video, camera, filesystem interaction , messaging, addressbook, networkaccount info, nativedevice application interaction;APIs behaviour

35. App content must adhere fully with Vodafone Terms and Conditions, Developer Guidelines and acceptance criteria e.g.:

36. the widget must not include any promoting services from other mobile operators or third party application stores;

37. the application must not contain any content which is unsuitable for all ages;

38. any advertising information (including help menu) inside the widget should comply with agreed content standards;

39. the application must not contain, promote or link to: graphic and gratuitous violence, including torture, sadism, mutilation, execution; content intended to shock or to be offensive; incitement or glamorising of illegal or anti-social behaviour such as illegal drug taking, solvent abuse; material that demonstrates criminal techniques;Content standards

41. International or special characters must bedisplayed correctly;

42. Interactive elements like buttons, links should not mislead their functionality and purposes;

43. The widget’s config.xml file must contain all URLs that the widget needs to connect to in order to function as described.Content standards