Last modified: 2014-07-15 20:17:56 UTC
The browser tests for MobileFrontend should be triggered by Gerrit just like it is going to be the case for ULS (bug 52120) or VisualEditor (bug 53691). The tests need to be carefully filtered out since they are expecting content or behavior which are not to be found on a freshly installed wiki. CC: - Zeljkof our Selenium Guru - Arthur our Mobile scrum master
Change 97497 had a related patch set uploaded by Hashar: browsertests: profile for default settings https://gerrit.wikimedia.org/r/97497
Most of the tests do not work against a freshly installed wiki. Either because of Watir timeout or because the test is expecting something which is only on some specific wiki. The features definition need a bunch of improvements before we can trigger the tests from Gerrit.
Patchset 9 of https://gerrit.wikimedia.org/r/#/c/97497/ pass on a fresh wiki with mobilefrontend having no specific configuration. That is done by ignoring any scenario relying on a specific feature/setting on the target wiki.
Change 97497 abandoned by Hashar: QA: profile for default settings Reason: Indeed those preferences have been moved elsewhere (mediawiki selenium gem). https://gerrit.wikimedia.org/r/97497
Adding Dan to this bug as his work on MF tests in Vagrant will probably inform some of this.