[Section Editing] Research Performance Time SPIKE
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	JTannerWMF
	Mar 4 2019, 3:54 PM

Description

During testing it was discovered by @dchan and @ppelberg that the performance varies by device and bandwidth and there is potential for improvements.

This ticket serves as a spike to investigate intentionally testing the Section Editing feature in different bandwidth environments and devices to determine areas of improvement.

Steps:

@ppelberg determine if this level of testing should happen pre or post deployment or at all
@ppelberg determine who should take lead on investigating further

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open		None	T209955 [EPIC: Focus] Isolate Section Editing
		Resolved		ppelberg	T217564 [Section Editing] Research Performance Time SPIKE

Event Timeline

JTannerWMF created this task.Mar 4 2019, 3:54 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 4 2019, 3:54 PM

JTannerWMF added a project: VisualEditor (Current work).Mar 4 2019, 3:54 PM

JTannerWMF added a parent task: T209955: [EPIC: Focus] Isolate Section Editing .

JTannerWMF edited projects, added VisualEditor; removed VisualEditor (Current work).Mar 4 2019, 4:01 PM

JTannerWMF moved this task from To Triage to Needs Discussion/Analysis on the VisualEditor board.

@dchan's foresight to intentionally test Section Editing on 1) entry level devices (i.e. Xiaomi Redmi 6A) and 2) with longer/bigger articles is a learning I think we should incorporate into future feature user testing.

As to what action we take on "1)" and "2)" in relation to Section Editing: at this point, I don't think any action should be taken. Instead – as @iamjessklein suggested – I think we should wrap up the user test we currently have running on MediaWiki and shift our focus to our upcoming release.