[QA] Browser tests coverage in MobileFrontend stable (Result of spike 1687)

[Jon Robson]

I ran an audit of the existing browser tests for MobileFrontend as
part of a mobile team spike [1]. You can see the results here:
https://www.mediawiki.org/wiki/Mobile/QA_Test_Audit_March_2014

Our coverage is actually not too bad, but there is definitely room
from improvement. That said I have a big concern is around the
organisation of the tests and how they are written and what is written
- many of the tests could do with being reworded and a lot of them
should probably actually be deleted. There is a lot of code
duplication.

When auditing I found tests scattered all over the place. This
suggests that we could benefit from reorganising the file structure to
be more logical, in particular features that relate to special pages
should have their own folder (this is particularly useful for
clarifying what tests the watch star and what tests the actual
watchlist page - Zeljko / Chris is it possible to have subfolders in
the features directory that contain features?).

I would also suggest the following actions for improving our test coverage:
* Add tests for error handling on login / account creation
* Add tests for this page has issues
* Improve tests for key editing and upload workflows
* Add tests for Language variant support
* Add tests for full text search support
* Improve the existing watch star tests so they actually check the end result
* Add test to check the user can close the left navigation menu
* Add tests for logout
* Add tests for reference overlay
* Add tests for toggling
* Add tests for Nearby in skins other than Minerva (mobile skin)
* Address hygiene issues on
https://www.mediawiki.org/wiki/Mobile/QA_Test_Audit_March_2014

[1] https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1687