###Test principles
- Any contributor who does not have sticky preference set should be included in A/B test
###Research questions*
//Does VE being the default mobile editing interface...//
- Increase edit completion rate?
- Increase the number of successful edits contributor make over a tbd period of time?
- Increase editor retention?
- Increase the number of switched-editor-type actions? (I.e. people fleeing back to wikitext.)
*See T221187
###Open questions
- [ ] How will we bucket users if we want to include contributors who are not logged in?
- [ ] What level of precision is appropriate for this A/B test?
- [ ] What wikis are being included in this A/B test? See T222803
- [ ] Confirm: we can distinguish between contributors who do and do not have a sticky editing interface preference set
- [ ] Confirm: what impact – in terms of scale – does including all contributors who do not have a sticky preference set on the number of edit sessions
- [ ] How long will the test last?
- [ ] How are we going to monitor the test? What will trigger us to interrupt the test?
- [ ] What are the range of actions we could take after the test concludes? What will determine which action(s) we take?
- [ ] What could we do to exclude editors from our edit completion rate numbers who we assume do not have any intention of completing an actual edit?
###"Done"
- [ ] A phabricator task is created that specifies how engineering should implement/instrument the A/B test