A controlled route is useful for checking calculations and UI states in a fitness app, while real outdoor testing remains necessary for sensor and GPS quality.
Define expected results
- Choose a route with a known approximate distance.
- Record the configured speed and expected duration.
- Define pause, resume and finish points.
- State whether the app should reject implausible speeds.
Run calculation checks
- Compare tracked distance with the route geometry.
- Check elapsed time versus moving time.
- Verify pace and speed units.
- Pause the mock route, resume it and inspect gaps or duplicate points.
Know the boundary
FlashGo supplies location coordinates. It does not generate heart rate, step count, barometer data, realistic GPS accuracy changes or physical motion. Test those inputs separately on appropriate hardware.
Common questions
Can mock GPS test step counting?
No. Step count comes from motion sensors or platform services, not GPS coordinates alone.
Can it test pace calculations?
Yes, for deterministic location-and-time inputs, but real GPS noise still needs field testing.
Use responsiblyReceiving apps can detect or reject mocked locations. Follow applicable laws and third-party terms; do not use FlashGo to mislead others or bypass restrictions.