Things to know about application testing on mobile devices

Tram Ho

Today, mobile applications are growing and expanding with diverse features such as dictionary applications, learning foreign languages, health check, playing games, taking pictures, listening to music, social networks, etc. This makes mobile phones a world of exciting experiences for users rather than just listening, calling and texting. And for these experiences to be useful, that is, the applications work optimally, the best quality possible when it comes to the users, the testing process is also widely deployed on mobile devices. , especially on smartphones. There are two types of testing on mobile devices: hardware testing and software testing:

  • Hardware testing: includes tests such as processor testing, resolution, screen size, RAM and Rom, Wifi, Bluetooth, … Hardware testing is also known as mobile testing
  • Software testing, also known as mobile application testing, is the act of testing the performance of apps installed on mobile devices.

People divide mobile applications into three categories:

1. Native Mobile App

  • La applications are written specifically for a type of platform such as iOS, Android, Windows Phone in the respective languages ​​of each platform (such as Java on Android, Object C on iOS, C # on Windowphone). Each Native App can only run on one platform and cannot be ported to other platforms, such as unable to bring iOS game apps to run in Android. For example, Native App is the current mobile game.

2. Web-based App

  • As web-based applications, users must use different browsers such as Chrome, Firefox, Safari to access the web-serve to use. They are written in web languages ​​like HTML5, CSS, Javascript or jQuery Mobile. In general, the interface and content of these applications will be the same as on the web because it is downloaded from the web. For example m.facebook.com .

3. Hybrid App

  • Also called hybrid applications because it is a combination of advantages between the two types to get the highest experience, can be run offline and online and use web-making techniques like HTML5 and CSS. The basic components are still written in the web language, but are placed in the native container so they can still be uploaded to the loading warehouse. For example Vnexpress is a hybrid news site application.

Some bullet points for testing applications on mobile devices

1. About installing and configuring the application

  • Which mobile device or tablet your client is requesting to test on (on my current iOS project, for example, on my iPhone 5SE, iPhone 6S and iPhone 8Plus), what is the screen size supported much (like 4.0 inches, 4.5 inches, etc.) to use the emulator and mobile devices to meet those requirements.
  • Where is the application to be tested stored? (memory card or internal memory of the phone)
  • The application works on many different devices, what is the synchronization?
  • Where can I download the application? Pay attention to cases like full memory or interruptions during the load
  • The initial installation process, removing and then reinstalling, should also be tested, taking into account interruptions
  • The process of updating the new version, if the user does not update, it will need to be tested

2. About the application’s UI

  • Background color, font color, lowercase letters, fonts like, does not match Design. Without Design, according to the testers feel, will the UI be confused with users, difficult to read and annoying?
  • Font size, size of the text boxes, buttons and left, right, center alignment, landscape mode (pan and tilt), are there any broken screens ….
  • Is the border of the text boxes, buttons, icons, … correct? Are their positions properly designed?
  • Text, tooltip, placeholder of buttons, long display name, instruction icons, warning message, display page content, …
  • Effects scroll down / up, pagination, page switch works
  • After leaving the screen to go to another page or reload the page / signout-signin to save the data
  • Depending on the specifications of each project, check if other effects such as swipe, touch, tap on, zoom in / ou, pinch, shake, etc. are working.
  • Keyboard used correctly, do not type out typos, …
  • Show if the header and footer are correct
  • Are the default values ​​(right after opening the screen) correct?
  • Tap multiple times at the same time on the image, will the image be enlarged / zoomed out, is the overall interface broken, is it still possible to work …

3. About the function of the application

  • Fully test the functions of the application to work as expected of KH in the original specification and design (pay attention to the max / min boundary values)
  • Test out-of-stream functions
  • Test these functions when losing network, Wifi connection, slow connection, airplane mode, 3G, 4G connection, …
  • Is it quick to click, rotate, swip, scroll, … fast?
  • The redirect of the links included in the application to the right page or log in to the Social links such as G +, Facebook
  • The time of the application, or when changing the settings in a mobile device, how the application works, is it affected, etc.
  • How does the application work in the case of locking the screen or using music applications, etc.
  • Confirm the synchronization when signing applications in different devices such as desktop, table, smartphone
  • With the application that can take pictures, test the ability to take pictures and after shooting, where are they stored
  • Test Notification from application such as update version / new feature, or reminder, ..
  • Pay attention to other cases such as when using the application, there will be incoming calls, messages, low battery, …
  • Test cases of system crash, …
  • Test the application when there are many active objects at the same time to see if it works well
  • Check whether the screen switching is smooth and accurate

4. About Performance and Load test

  • Check how long it takes the app to open for users to use
  • Is the response of the application’s processing within the time allowed?
  • See how much resources are consumed by the application, such as how much battery it consumes
  • Check the device memory consumption of the application
  • Test the parallel running of many other applications at the same time while using the application under test
  • Restoring the application after a long period of use, etc.In addition, we also need to pay attention to testing the application’s user-friendliness (such as providing user instructions, simple text). , clear menu, …), application compatibility across multiple hardware / software platforms, operating systems, network environments (such as performing application operations on Chrome, Safari, IE or when changing from 3G / 4G to use Wifi or the application works well when there are many connections such as Bluetooth / Wifi / cable, …), the ability to interact with other applications on the same mobile device with the application under test, Monkey testing, Security Test, Location test, …
Share the news now

Source : Viblo