Background

Readers teams are currently designing experiments that operate on article content. Supporting Parsoid and legacy parser for these experiments is sometimes a necessity due to the fact that the different projects we run on have different states. For example, at time of writing English Wikipedia is currently using the legacy parser and Italian Wikipedia is using Parsoid. This is particularly challenging on mobile where the HTML markup is considerably different depending on the parser.

We hope to have Parsoid everywhere as the default parser by the end of Q4. When that happens many logged in users might opt out and using legacy parser, it would be useful to have support in test kitchen for restricting new experiments to Parsoid content only (e.g. exclude people using the legacy parser).

Having such an option now would also allow teams to consider this in the development of their experiments.

At minimum we should have a field in all events for the parser type that allow analysts to filter out people if they are not legible for the experiment in a similar way to skins.

User story

As a product manager running experiments I want to run experiments on a known configuration for logged in users.

Requirements

• It is possible in test kitchen to configure an experiment so it never runs on users who are using the legacy parser

BDD

• For QA engineer to fill out

Test Steps

• For QA engineer to fill out

Design

• Add mockups and design requirements

Acceptance criteria

• Add acceptance criteria

Communication criteria - does this need an announcement or discussion?

• Add communication criteria

Rollback plan

• What is the rollback plan in production for this task if something goes wrong?

This task was created by Version 1.2.0 of the Web team task template using phabulous