Today, more and more companies are not just considering mobile as a necessary platform, but also considering mobile as the only platform. Obviously, developers hope their applications gain market share and user acceptance, but this depends on its quality. One of the (many) things that organizations overlook regarding their mobile application software testing are that the conflicts for their application with the OS and/or other software applications on the phone have countless scenarios.
Some of the considerations for testing conflicts in mobile applications where the application should pause and then return to the departure point include:

  1. Background and foreground the app
  2. Change orientation
  3. Incoming call/video call while using
  4. Background the app, change orientation & then foreground the app
  5. Lock and unlock the screen while using the app
  6. One sms come in while using
  7. Set device to AIRPLANE mode

Additionally, other inherent parts of the operating system should be tested to see how they interact with the application especially when competing for similar resources. Examples include:

  1. Launch recorder, especially for audio related app.
  2. Launch camera, especially for video related app.
  3. Launch the same type apps. (such as launching MSN while Skype is running)

Resource utilization warnings and upgrade notifications and warnings should also be tested. Examples include:

  1. Disk is full
  2. Upgrade to old version

In these cases, proper tips as “Disk is full, please remove older data” or “Upgrade to old version is not allowed” should appear.

As you can see, there are many scenarios such as those above where conflicts are possible. Thest types of tests can often be automated depending on the maturity of the application. Your application needs to be able to respond to, or not respond to many of these potential conflicts to ensure its robustness, just one of the many things to worry about when planning your mobile software application testing.