7 Tips on How to Plan Your Mobile Testing

7 Tips on How to Plan Your Mobile Testing
November 30 10:00 2012 Print This Article

If you plan to conduct any type of software testing, the first thing you should do is plan it.

We offer you some hints on how to plan one of the most popular types of software testing, i.e. mobile testing.


7 Tips on What to Consider When Planning Mobile Testing:

  1. Consider uniting the elements of manual testing with automated testing. Mind that manual testing takes much time, so you’d better find a way to automate certain parts of it.
  2. When planning automation, consider the test automation tools you have. In case you don’t have the needed one, consider creating it yourself (if you have enough time, skills and resources of course).
  3. Sometimes software testing is more effective and productive if the code is split apart. Although you may consider it to be extra work, it may smooth things down for you.
  4. Use divide-and-conquer method. Remember that mobile client code differs from server code due to certain restrictions put on the development platform and the need for application optimization and its small size.
  5. Use automated testing elements for build and deployment processes. It will accelerate the overall testing process and reduce the risk of human mistake.
  6. Find all the possible way to provide effective test output to optimize the problem identification and addressing.
  7. Consider using some simple tools that may help you greatly improve your mobile testing.

Tools that May Help You in Testing:

  • User-agent capture tools;
  • SMS messages as ways of sending URLs and download links to devices;
  • Screen-capture tools;
  • Tools that collect several screenshots in a single display.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles
  • http://www.keynotedeviceanywhere.com Josh

    This is a great list! Thanks for your suggestions. Our customers find they run into the same issues. And planning is KEY to any mobile app or website testing strategy. Check out this free tool for example to help start to plan which devices to begin testing on for manual or automated testing – http://www.keynotedeviceanywhere.com/mobile-device-planner.html

  • http://www.perfectpitchmarketinginc.com JeanAnn Harrison

    Tips 1 & 2 are good tips. What people fail to realize there is “no one size fits all” tool to complete all your mobile testing. A combination and recognizing what can be automated has to be planned before testing begins.

    I’m unsure what you’re trying to convey in Tips #3 & #4. One of the most effective way to test mobile software is to COMBINE your types of tests so you are efficient in your test coverage. One tip I talk about in every presentation I do: Know your architecture. If you can work closely with your development team, learn how the software communicates out to the network, how does a data search is conducted. By this I mean, what inter-dependencies exist when performing certain functions. If you know your architecture, then you can design stronger tests which cover more than just testing an application GUI.

    Tip #5 talks about automating build and deployment, but what about a tip on testing the installation of software onto the device? There is so much more to testing installation on mobile devices, including testing your automated software. What if the mobile device (not a phone or tablet) requires installation of a proprietary operating system? If your list is for mobile phones and tablets only, then this should be a caveat at the beginning of the blog.

    Tip #6 – I have no idea what message you are trying to convey. Could you please explain?

    Tip #7 – I find this tip far too general and almost as if you were reaching for a seventh tip to add to this list.

    Mobile testing requires technical knowledge of not only software but hardware and operating systems. Testers need to test drivers like notification LED lights which work with their software application and recognize when a bug is in the OS rather than the software application. This is not true of client/server or web application testers. What about how your software behaves while the device is charging? Do you test your software’s behavior to include various hardware conditions? Were you aware if the device reaches a too high internal temperature any data transmitted out could be corrupt if the software doesn’t regulate what is acceptable internal temperature? Software can turn on/off cell modems based on hardware conditions but mobile software teams need to be aware.

    Again, the first two tips are good. I would kindly ask you revisit your other tips.