In theory yes but it would mean abstracting a native function and writing new JavaScript that routes around the request for the user's location so it wouldn't be a true test and arguably not of any more value then no tests.
To avoid a profile, if possible we could do one of the following: 1) stub the native browser JavaScript function navigator.getCurrentLocation so that it does something else 2) Automate the clicking of the share current location confirmation message (we do this for confirm dialogues - not sure if possible for share location dialogs..) On Tue, Mar 18, 2014 at 3:11 PM, Chris McMahon <[email protected]> wrote: > > > > On Tue, Mar 18, 2014 at 2:22 PM, Jon Robson <[email protected]> wrote: >> >> Usually the things that break are simply >> loading it in the first place which can really only be tested with a >> browser test. > > > Can "loading it in the first place" be tested without having to maintain a > custom profile for Firefox that overrides default settings for access to > browser location information? _______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
