1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

5 Rules for Testing Mobile Applications

Discussion in 'BlackHat Lounge' started by keenmobi, Apr 21, 2017.

  1. keenmobi

    keenmobi BANNED BANNED

    Mar 24, 2017
    Likes Received:
    Any development of mobile applications (Android, iOS or other OS) requires the scrupulous testing. There are a lot of nuances, the task of which is to make the product as high-quality and stable as possible.


    Human factor.
    Perhaps this is the main point, because people determine the quality and the monetization of the application and its popularity depend on users. Naturally, the experienced developer and user are completely different categories, and therefore, first of all, it is necessary to conduct the user-cases on acquaintances and relatives. It's better if these people are far from programming. A good experience is testing on young children. A chaotic and illogical button press is inherent for some people, so it's best to know how your development will react in such conditions.

    Features of operation systems.
    It is important to understand how much RAM the device uses, whether the system can auto-delete it. Search for leaks, boundary conditions, etc. There are significant differences between iOS and Android from desktop applications, so it is very important to study the broad receivers, activity,

    Mobile applications can be interrupted by a call, a pop-up reminder, an alarm clock by a messenger. This is the most important stage, so after the functional testing, be sure to check the product response to a forced interruption.

    Check connection.
    There are four basic methods of verification:
    • Loss of communication;
    • Lack of communication;
    • Positive case;
    • Permanent bond of average quality.
    • Mobility

    Change the performance
    from the background with a preliminary change in position and orientation of the screen;