Reasons to Become a Mobile Application Tester

I saw a post recently on that listed the Top 10 Reasons to Become a Mobile Application Tester.  I agree with all 10 reasons, however, I’m going to give a couple more reasons. 

1. Mobile application testers are in high demand!

Here’s another post on that talks about the growing demand of mobile application developers and testers. To see how true this is, I did a search for “mobile developer” on and got back 1,890 results. Of course, this doesn’t include other searches like “mobile engineer” (2,228 results) and “mobile programmer” (215 results).

Next, I performed a search for “mobile tester” and got back 104 results and “mobile QA engineer” (322 results).  These numbers are small in comparison, however, this shows that the demand is there.  I believe this number will grow even more after companies realize they need a software tester with expertise in mobile testing because their developers cannot double task or do not deliver the quality mobile applications they desire.

2. There are more defects to be found.

The lack of mobile developers will force companies to transition existing developers (or hire new ones) to mobile development.  Some might put these developers through training, but it’s highly unlikely that they will have the money to do that. What’s this mean? That’s right…more defects.


Strategically Placing Testing Resources for Maximum Test Effectiveness

No, I am not talking about test resource management (i.e. placing testing consultants at certain clients to maximize profits) or anything like that.  I’m strictly speaking about test leads/test managers assigning their testing resources to specific areas of an application in order to provide maximum test effectiveness during test planning, test creation, test execution, and result analysis.

At my current client we discovered gaps in our testing by assigning two testing resources to different areas of the system that overlap. For example, my area of the system dealt with defining data in the system that will determine what happens (e.g. when a flag is triggered, what prompts appear to the user, etc.) in another part of the system. The other part of the system was assigned to a different tester. Therefore, the other tester used my test scripts to write his and whala! Gaps discovered!