• Save
Vodafone 360 widget QA guidelines
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Vodafone 360 widget QA guidelines

on

  • 1,218 views

 

Statistics

Views

Total Views
1,218
Views on SlideShare
1,114
Embed Views
104

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 104

http://developer.vodafone.com 101
https://developer.vodafone.com 2
http://devportalsit.vfnet.de 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Vodafone 360 widget QA guidelines Presentation Transcript

  • 1. Vodafone 360 widget QA
    Guidelines for developers
    By Mobica
  • 2. Plan of thepresentation
    • Purpose of thepresentation
    • 3. Problems and most commonreasons of rejections
    • 4. A scope of testing
    • 5. How to pass the QA process? – Tips for developers
    • 6. Discussion
  • Purpose of the presentation
    This presentation provides guidelines for elements and features that we check when testing your applications.Before submitting your app, we recommend that you ensure these criteria have been met, to reduce the time it takes to approve your app and increase chances of passing first time round.
  • 7. Problems and most common reasons of rejections
    A lot of widgets are failing many times because of similar problems:
    • Widgets do not adapt to the screen resolution either in portrait mode or landscape mode
    • 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
  • 12. Scope of testing
    • Widget execution
    • 13. Navigation
    • 14. Extendedmode/Dockedmode
    • 15. Contentstandards
    • 16. APIsbehavior
    • 17. System resources: data traffic, memoryconsumption, batteryusage
    • 18. Update
    • 19. Functionalcheck
  • QA criteria - Tips for developers
    • Widget size less than 3MB;
    • 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
  • 25. QA criteria - Tips for developers
    • Widgetadapts to thescreen resolutioncorrectly - portrait / landscapemode (ifsupported);
    • 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
  • 30. QA criteria - Tips for developers
    • Text must be legible and images must not be pixelated or of poor quality;
    • 31. The extended mode/dockedmode content must not display a static image or information which is not updated;
    Extended mode/Docked mode
    • Widgets which use APIs must execute correctly, show correct UE behavior and behave securely;
    • 32. Lunching or closing API doesn`tcrashorclosethewidget;
    • 33. SupportedAPIs: GPS, audio/video, camera, filesystem interaction , messaging, addressbook, networkaccount info, nativedevice application interaction;
    APIs behaviour
  • 34. QA criteria - Tips for developers
    • Sufficient and accurate information insidethe widget, instructions and help provided, pricing information available;
    • 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
  • 40. QA criteria - Tips for developers
    • The widget must display information that is appropriate to the selected language;
    • 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
  • 44. QA criteria - Tips for developers
    • System resources must be used efficiently to ensure good user experience;
    • 45. Widget usesreasonableamountof power and memory and doesn`tgenerate large volumes of data traffic without good reason;
    System Resources
    • The widget must update (ifavailable) without any errors and run correctly after being updated;
    Update
    • Providedby the developer or created by the testers according to widget specification, attempt to break yourapp.
    Fuctional check