CIO OPINION
• Network connectivity interference from Bluetooth devices .
• Low battery power on mobile devices , which could decrease hardware performance
• Low proximity to wireless access points , causing devices to vacillate between using a Wi-Fi connection or relying on the cellular network for connectivity
These are all circumstances that occur regularly in the real world , as virtually anyone who owns a smartphone , tablet or any other type of mobile device knows all too well .
Unfortunately , not all mobile testing strategies address the possibility of circumstances like those described above . impossible to evaluate what happens when physical infrastructure runs suboptimally because there is no physical infrastructure or they test on well-maintained , fully charged real devices .
For most testing needs , it makes good sense to test under best-case conditions . A stable testing environment removes many of the ancillary environment variables that could leave engineers wondering whether a failed mobile test resulted from a problem with the application they are testing or from an environmental factor beyond their control , such as a weak network connection . Thus , in many cases , you don ’ t want chaos to be part of your mobile testing workflows .
The benefits of chaos testing for mobile software tests
Typically , teams run mobile tests under conditions that are as close as possible to ideal . They test either using mobile device simulators , where it ’ s simply
That said , there are situations where being able to inject chaos into some of your mobile tests is highly valuable .
www . intelligentcio . com INTELLIGENTCIO LATAM 45