in Mobile
50 shades of mobile testing
In fact, the mobile testing palette contains much more shades. Along with testing any other applications, testing mobile applications has become a separate QA sector.
In fact, the mobile testing palette contains much more shades. Along with testing any other applications, testing mobile applications has become a separate QA sector. In this post, we're going to explain some of the nuances of mobile testing.
To begin with, let's shed some light on the differences between testing desktop and mobile applications. The fundamental differences here lie in the user's behavior.
Desktop applications are mostly used in a relaxed atmosphere at home or office. The user sits in a comfortable chair behind the large screen, slowly switching between tabs. He is ready for not only consuming the information but also to forgive the developers for most of their mistakes. Even the horizontal slider at the browser's bottom. A user has TIME for it.
Desktop applications are mostly used in a relaxed atmosphere at home or office. The user sits in a comfortable chair behind the large screen, slowly switching between tabs. He is ready for not only consuming the information but also to forgive the developers for most of their mistakes. Even the horizontal slider at the browser's bottom. A user has TIME for it.
To begin with, let's shed some light on the differences between testing desktop and mobile applications. The fundamental differences here lie in the user's behavior.
Desktop applications are mostly used in a relaxed atmosphere at home or office. The user sits in a comfortable chair behind the large screen, slowly switching between tabs. He is ready for not only consuming the information but also to forgive the developers for most of their mistakes. Even the horizontal slider at the browser's bottom. A user has TIME for it.
Desktop applications are mostly used in a relaxed atmosphere at home or office. The user sits in a comfortable chair behind the large screen, slowly switching between tabs. He is ready for not only consuming the information but also to forgive the developers for most of their mistakes. Even the horizontal slider at the browser's bottom. A user has TIME for it.
Mobile applications are usually used on the go, so a small monitor screen and noisy environment can greatly affect the user's perception because now there is NO TIME.
A user goes to the interview, quickly loading the map to find the right building
A user shivers from the cold at the bus stop and every 30 seconds updates the application with the public transport schedule
A user receives an important SMS message and immediately puts it in the to-do list application
1
2
3
A user reads an e-book in the subway while music plays in the headset
A user can be in the elevator, in the taxi, and can be very angry if the Instagram pictures are loaded for a long time
And user's kids are going insane if a new game they just downloaded shows the boot screen longer than they blink
4
5
6
These seemingly simple and clear user actions contain a large number of challenges for mobile developers. For the user does not delete the mobile application 30 seconds after its installation, the latter must be intuitive, fast, and work stably in all conditions. Developers sometimes go through the hell and high water to win the princess user's heart.
These seemingly simple and clear user actions contain a large number of challenges for mobile developers. For the user does not delete the mobile application 30 seconds after its installation, the latter must be intuitive, fast, and work stably in all conditions. Developers sometimes go through the hell and high water to win the princess user's heart.
But the killing of the dragon goes to testers. Just take a look what a tester needs to do:
But the killing of the dragon goes to testers. Just take a look what a tester needs to do:
Mobile App Check List
- Select devices for testing (physical devices, emulators, simulators). This is especially true of Android applications, as the device market here is striking in its scale
- Take into account the features of the operating system associated with the installation, removal, and updating of the application
- Correctly configure the operation of the hard buttons of the device
- Test the application in any network (Wi-Fi, 3G, 4G, Edge etc.) and take into account all the features of the application's interaction with networks
- Eliminate the crash of the application in case of interruption and switching (phone call, SMS)
- Ensure proper testing of the graphical and logical interfaces of the project (UI / UX)
- Check the memory load
- Check the localization (for example, double check the presence of hieroglyphs in the English Android menu)
- Eliminate excessive power consumption
- Pray (NOTE: the prayers are separate for each version of iOS)
Mobile App Check List
- Select devices for testing (physical devices, emulators, simulators). This is especially true of Android applications, as the device market here is striking in its scale
- Take into account the features of the operating system associated with the installation, removal, and updating of the application
- Correctly configure the operation of the hard buttons of the device
- Test the application in any network (Wi-Fi, 3G, 4G, Edge etc.) and take into account all the features of the application's interaction with networks
- Eliminate the crash of the application in case of interruption and switching (phone call, SMS)
- Ensure proper testing of the graphical and logical interfaces of the project (UI / UX)
- Check the memory load
- Check the localization (for example, double check the presence of hieroglyphs in the English Android menu)
- Eliminate excessive power consumption
- Pray (NOTE: the prayers are separate for each version of iOS)
These, of course, not all the questions that arise when testing a mobile application. Nevertheless, even a brief acquaintance with them gives an idea of the complexity of this process.
In one of the following posts, we will talk about how Android testing differs from iOS testing and why testers spend quite a lot of hit points on an Android dragon.
In one of the following posts, we will talk about how Android testing differs from iOS testing and why testers spend quite a lot of hit points on an Android dragon.
These, of course, not all the questions that arise when testing a mobile application. Nevertheless, even a brief acquaintance with them gives an idea of the complexity of this process.
In one of the following posts, we will talk about how Android testing differs from iOS testing and why testers spend quite a lot of hit points on an Android dragon.
In one of the following posts, we will talk about how Android testing differs from iOS testing and why testers spend quite a lot of hit points on an Android dragon.
We love what we do and do it with pleasure. See you later!
QA Camp team
You may also like: