Mobile website testing is little different from traditional website testing procedures. We normally use different browsers for traditional website testing - [Ex: Internet Explorer (all recent versions), Firefox(all recent versions), Opera (all recent versions), and Apple Safari – now days Google Chrome also added in the list. But for Mobile websites we follow a different strategy.
- Test cases should be based on different devices and its functional capacity – Ex: processing speed, battery level etc.
- Test cases should be executed in different real devices and different browsers in same device. Sometime, a same device will do different things with different browsers. The screen size and the network also matters in performance.
- Emulators and Online Standard verifications should be used for DotMobi Compliance Tests – Ex: ready.modi – The result should be atleast 4/5 for quality.
- Data Access, external application access should be verified – Ex: Video Play, Upload Picture etc.
- The Testing should happen from the early stages of development itself to avoid major issues in final stages. The Testers should have awareness about devices, Device specifications, Mobile internet browser specifications, settings and knowledge about other mobi websites too.
- A quality standard document should be prepared and published with all design and development guidelines, and it should be followed strictly. If the developers are using Wordpress Templates or Joomla Templates, the same verification strategy should be applied – if required the customization should be done.
- The performance [download image & media], and non-functional [clear view] should be verified before certification.
Testing is basically a common sense activity with little knowledge on usability. Mobile website testing, and mobile application testing varies with little differences, but a Skillful tester can easily manage both the areas.
No comments:
Post a Comment