On Tue, Mar 18, 2014 at 7:36 PM, Jon Robson jrobson@wikimedia.org wrote:
Setting the cookie mf_useformat ensures that the mobile site gets loaded. If tests are run against en.m. etc.. this won't have any effect, but a lot of local instances are setup to run the desktop URL by default. An alternative way of doing this would be to toggle to the mobile site explicitly in the test suite.
e.g. Given /^I am in the mobile view$/ do on(ArticlePage).switch_to_mobile_element.click end
In terms of 2nd question - no I don't think we should abandon trying to test Nearby in the browser, it is one of our most important features and has extremely inadequate test coverage and is one of the things that seems to break the most. Even if the test only works for Firefox, having that test is a good thing.
Chris and I have paired on this. We have left setting the cookie in the mobile fronted repository[1] but we have removed the code for starting a browser with custom profile, needed for nearby tests. The code was deleted because we were able to set the custom profile only on a local machine, meaning the test was not running on jenkins machine. If you want to run this test on jenkins, then we have to figure a way to make the custom profile work with remote browsers.
If you have any questions, let me know.
Željko -- 1: https://gerrit.wikimedia.org/r/#/c/119271/11/tests/browser/features/support/...