Background
In order to best position ourselves to be able to run this A/B test successfully, there are some questions we need answered, and some understanding of the new system that should be gained before we can finish scoping the total body of work to be done. Practically speaking, this ticket will encompass an engineer (@SToyofuku-WMF, although of course others are welcome to pair!) working closely with both experiment platform and web to answer questions we can foresee and create tickets in the sprint backlog that are well-scoped, estimated, and ready for inclusion in the following sprint (Sprint 6)
User story
As a member of the web team that is not Steph, I want to understand the work that will be done as part of the donation A/B test, so that I can participate if I wish
Requirements
- All tickets we anticipate needing for this project are created under the epic and at least the work for the upcoming Sprint 6 is estimated
- All open questions are answered:
- What does local development of experiments look like?
- How can we render the specced donate link in vector (with a heart icon in the user links menu)?
-
How can we render the specced donate mini banner in minerva (with bolded text translated into multiple languages rendered via mustache template)?descoped - What does configuration of experiments look like locally, in beta, and in prod; both pre- and post- launch?
- How can we test all three paths for both mobile and desktop given that this is a logged-out experiment?
- A proof of concept for at least one of the experiences (either mobile or desktop) is uploaded
- with instructions for manually testing locally
- including minimum viable instrumentation
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
Most up to date designs are in T388149
Acceptance criteria
A bit vaguely defined but, we should all feel that we understand broadly how this project will look, that outstanding questions have been answered, and that nobody is stressed or apprehensive about the work being included beginning in Sprint 6
Communication criteria - does this need an announcement or discussion?
The engineer working on this ticket (assumed to be Steph) should keep both Olga/Jan updated on the high-level progress of scoping the overall project, as well as keep the team updated on tasks created/that will need to be estimated. Do not ask people to estimate 7+ tickets the day before the sprint starts!!
Rollback plan
Nothing is being deployed, so rollback here is reverting ticket bodies or having follow-up conversations