Page MenuHomePhabricator

Two week sprint: improve UI test coverage in VisualEditor
Closed, DeclinedPublic

Description

In the Editing team planning meeting held on Thursday 5th July 2018, the team discussed the large number of regressions that happen in the editing space. Fixing regressions accounts for a large proportion of the team's time, and prevents the team from working on new features.

One area that the team finds deficient is UI test coverage. With good UI tests, regressions are more likely to present themselves before a patch is merged rather than after it, making it easier to fix them at the time and reducing the overall time spent dealing with them.

For the next two weeks (i.e. until Friday 20th July 2018) the team will spend time improving UI test coverage to reduce future regressions.

Snapshot of test coverage from Friday 6th July 2018:

Screen Shot 2018-07-06 at 14.33.27.png (990×1 px, 141 KB)

Event Timeline

Deskana triaged this task as High priority.
Deskana moved this task from Incoming to In progress on the VisualEditor (Current work) board.

I think the first step is to have a technical meeting where we go through the uncovered files, and work out what we can actually write tests for, then assign smaller tasks to specific people.

@Esanders: Is that something that could actually be done in a meeting or would a spike be more appropriate?

If it would be helpful/motivational, I can set up a chart similar to https://tools.wmflabs.org/coverage/mediawiki/chart.png for VisualEditor coverage.

This sprint didn't end up happening, and doing another sprint on this in the near future is not under consideration right now.