Page MenuHomePhabricator

VisualEditor: Create browser tests for using VE via Mobile UI
Open, MediumPublicFeature

Description

Author: jhall

Description:
The time has come to create additional VisualEditor browser tests for accessing VE via the Mobile interface.

James F had great feedback on which repo (MobilefrontEnd vs. VisualEditor) these tests belong in:

"​One way of looking at it is on the blocking model. If (when!) these tests were to block merge, which repo's changes should they be triggered by? In this case, I think there's a case for some basic browser tests for VE-on-Mobile to be in VisualEditor (specifically, in the MediaWiki VisualEditor repo) with the major tests be in MobileFrontend."

An example URL for accessing VE via Mobile UI is: [1]

[1] http://en.m.wikipedia.beta.wmflabs.org/wiki/0.04730373828804457?mobileaction=alpha#editor/0


Version: unspecified
Severity: enhancement

Details

Reference
bz60290

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:52 AM
bzimport set Reference to bz60290.

Change 108987 had a related patch set uploaded by Jhall:
[Browser test] WIP New test(s) for editing with VisualEditor via mobile user interface.

https://gerrit.wikimedia.org/r/108987

jhall wrote:

Setting status back to ASSIGNED since Gerrit is a little over-eager to mark even WIP patch sets as being ready for review!

Change 108987 abandoned by Jforrester:
[Browser test] WIP New test(s) for editing with VisualEditor via mobile user interface.

Reason:
Not currently being worked on AFAICT.

https://gerrit.wikimedia.org/r/108987

Jdforrester-WMF lowered the priority of this task from High to Medium.Jan 9 2015, 10:38 PM
Cmcmahon set Security to None.

I'll take this on. Having refactored both MF and VE at the end of 2014, both repos are in good shape to support new feature coverage.

I'll take this on. Having refactored both MF and VE at the end of 2014, both repos are in good shape to support new feature coverage.

Awesome. :-)

So.. MobileFrontend has some basic ones [1]. I wonder if we should have a dedicated extension for MobileFrontendVETests that depends on MobileFrontend and VisualEditor? It seems silly having two (might even be worth breaking out MobileFrontendVE into its own extension?)

[1] e.g. https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome-sauce/440/testReport/(root)/VisualEditor%20Mobile/I_can_edit_a_page_using_VisualEditor/

greg removed a subscriber: Cmcmahon.

In the Triage meeting we felt that this wasn't a clear enough ask for Q4.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 12:23 PM
Aklapper removed a subscriber: rmoen.