Testing Significant Location Change

We are currently developing a research-based iOS application that relies heavily on background capabilities, specifically Significant Location Change.

We are using CLLocationManager.startMonitoringSignificantLocationChanges().

During development, when using DebugSimulate Location in Xcode, we receive a location update only once. Subsequent simulated location changes do not trigger additional callbacks, which makes testing and development quite cumbersome.

Are there any tools, commands, or workflows (e.g., via Xcode, Instruments, or system-level simulation) to reliably simulate multiple significant location change callbacks for testing purposes?

If there aren't such tools, how do I test this behaviour reliably, robustly and rigidly?

Answered by Engineer in 874589022

You would want to use the Simulator's Features -> Location to test how your app handles location updates.

But eventually, for testing background capabilities, the only reliable test would be to run the app on a physical device while it is standalone, not connected to Xcode - for which you would want to implement your own logging and testing methodology within the app - and for location apps, actually travel, as simulated locations are going to perform better than real ones, and if testing background capabilities attached to Xcode, you will not get a real life demonstration of how your app performs, as debugging via Xcode will give it additional capabilities to assist in debugging your code, but will not show what your customers will eventually experience.

Accepted Answer

You would want to use the Simulator's Features -> Location to test how your app handles location updates.

But eventually, for testing background capabilities, the only reliable test would be to run the app on a physical device while it is standalone, not connected to Xcode - for which you would want to implement your own logging and testing methodology within the app - and for location apps, actually travel, as simulated locations are going to perform better than real ones, and if testing background capabilities attached to Xcode, you will not get a real life demonstration of how your app performs, as debugging via Xcode will give it additional capabilities to assist in debugging your code, but will not show what your customers will eventually experience.

Testing Significant Location Change
 
 
Q