
What makes up a solid mobile tester? If you were searching for someone to join your mobile testing team or want to try this career, what kinds of qualities do you need? As I’ve discussed in previous blogs, mobile testers do not JUST test the software as if it were a desktop application. Mobile testers must have a different perspective of how to go about their jobs. So let’s break down the types of tests needed and to uncover qualities to make up that solid mobile tester.
Mobile devices and those applications which work off of mobile devices are entire systems. A client/server application does not require the tester to test the server, how the database would store data, but instead will test data travelling back and forth to the server. What application tester will test the servers’ drivers? Does the application tester consider testing network communication existence beyond the connection itself? Can the device remain in sync at various locations? Is the device clock updated, especially after moving the device to different locations? Many mobile applications will use the LED notification lights for a purpose, check wifi networks when location changes, check to make sure the application is in sync, update the time if the application uses/records time from the device clock. And let’s not forget the hardware tests affecting software behavior which is rarely a consideration for a client/server application tester.
The mobile tester needs to understand the entire architecture of the mobile device’s system including hardware, firmware and interaction with the software. As I’ve previously referred in earlier blog posts, charging the device while engaging with the software can create interesting overall system behavior which may not be acceptable to the user or customer. The mobile tester should be prepared to breaking down the system, and the mobile tester must be comfortable reading log files, not afraid to read code and consider all different perspectives.
Mobile testers tend to be system integration testers. The types of tests a system integration tester performs help to develop the skill of expanding perspective. Seeing beyond the GUI tests, considering possible behavior patterns, asking “what if…” all help the system integration tester and mobile tester.
How can you find someone to do mobile testing? The experience can be stated but the tester must prove they can do mobile testing by describing their tests. Mobile testers spend time on performance tests and those tests rarely consider load testing. Quite simply, interactions on the mobile device are singular and not reliant on the number of users. Load testing from a traditional sense is not part of a mobile tester’s set of tasks. Performance tests are not traditional, and mobile testers think differently. A great example of a mobile performance test is how network communication is maintained while charging the mobile device. Add the idea of charging the device and then changing up variables to create more functional tests. Observe the performance of the software during these tests which will reveal more about the software application’s behavior.
If a hiring manager is looking for a mobile tester or someone capable of performing mobile testing, the hiring manager might ask questions about regarding the ability to look at a situation in many different ways. Can the candidate apply skills to new situations? Is the candidate capable of combining tests and changing up conditions to create new test situations? Mobile testers have to see and test in multiple levels. GUI and functional testers rarely test on multiple levels and find it difficult to see different perspectives.
Next up: Mobile tests for the mobile website. Why is testing a mobile site different than desktop website? What considerations do you include in your tests? Please feel free to leave your thoughts, suggestions or questions as comments. Reminder, no comments will be published if not commenting on the specific blog post.
Qualities for a Mobile Tester