Gone are the days when the need for mobile app testing had to be promoted, especially when a lot of the development was being done by start-ups and freelancers. Today, the need for quality in mobile applications is a given, that all organizations understand fairly well.
This maturity has come not just from organizations understanding the need but also a fairly established market with end users who care for quality, engineers who understand how to make quality seamless in mobile and non-mobile applications, tool vendors who offer adequate support for mobile app testing, OS makers who provide in built support etc. For example, there are automation solutions both in built and specific to mobile operating systems including XC Test, Espresso. Log views, dumps, tools to support more test scenarios are all more openly available through the operating system itself today. For example, one area where mobile apps was falling short was a defined strategy for special test attributes such as accessibility – while the guidelines (such as WCAG, Sec 508) are not specifically available for mobile applications, there is enough support to bring in iOS app testing and Android app testing leveraging existing guidelines and tools such as talkback, voiceover which all support specialized testing for mobile operating systems.
Today we are at a state where although specific guidelines (be it security, localization, accessibility) may not be available for mobile operating systems, enough tools are available, teams have the understanding and experience implementing and there is stakeholder buy in on the importance of functional and non-functional quality that makes the mobile app testing market one with lot of maturity and scope for the years to come.