You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it currently stands, I'm just using real-world data to test Geohash Droid features. This works for most cases, but when I need to make sure something triggers (or does NOT trigger) when certain conditions are met, I currently have little choice but to wait until those conditions happen in the real world. Most notable would be the Known Locations feature, where I need to arrange a hashpoint to trigger notifications (as well as make sure neighboring graticules won't trigger if the graticule restriction option is set). As it stands, all I can do is just set up a cloud of Known Locations and hope one of them triggers, then check to see if it did what I wanted it to do.
The major problem here is the app's current strong dependency on the stock cache. Tossing in fake points for testing would invariably poison that cache with bogus data unless I take care to make sure the testing stuff never enters the cache (and never reads the cache, either). I'd need to rewrite significant parts in order to allow for testing hooks like that. It's plausible, just not the simplest thing I can think of.
The text was updated successfully, but these errors were encountered:
As it currently stands, I'm just using real-world data to test Geohash Droid features. This works for most cases, but when I need to make sure something triggers (or does NOT trigger) when certain conditions are met, I currently have little choice but to wait until those conditions happen in the real world. Most notable would be the Known Locations feature, where I need to arrange a hashpoint to trigger notifications (as well as make sure neighboring graticules won't trigger if the graticule restriction option is set). As it stands, all I can do is just set up a cloud of Known Locations and hope one of them triggers, then check to see if it did what I wanted it to do.
The major problem here is the app's current strong dependency on the stock cache. Tossing in fake points for testing would invariably poison that cache with bogus data unless I take care to make sure the testing stuff never enters the cache (and never reads the cache, either). I'd need to rewrite significant parts in order to allow for testing hooks like that. It's plausible, just not the simplest thing I can think of.
The text was updated successfully, but these errors were encountered: