Background

The account creation workflow has been built over several tickets. QA is a requirement before we deploy to production.

User story

• As a QA engineer, I want to check CTA user workflow instrumentation, so that all events triggered by users are recorded as per this document - Account Creation Reading List CTA Instrumentation Spec

Requirements

The following tickets have been QAed

• T422174: Account Creation CTA experiment: track experiment exposure
• T422175: Account Creation CTA experiment: track clicks for control group
• T422176: Account Creation CTA experiment: track clicks for treatment group
• T422177: Account Creation CTA experiment: track account creations for treatment group
• T422169: Account Creation CTA experiment: handle experience after account creation
• T425372: Account Creation CTA experiment: track account creations for control group

BDD

Scenario 1 Non-logged user in a control group clicks the watchstar icon

Given a non-logged user in a control group sees the watchstar icon
When a user clicks on the watchstar icon and sees the drawer with "Login" and "Sign up" links
Then a user clicks on "Sign up" and and gets redirected to the "Create account page"
And a user's actions are recorded as events

Scenario 2 Non-logged user in a treatment group clicks the bookmark icon

Given a non-logged user in a treatment group sees the bookmark icon
When a user clicks on the bookmark icon and sees the popover with "Create account" and "Log in" links
Then a user clicks on "Create account" and gets redirected to the "Create account page"
And a user's actions are recorded as events

Test Steps

• check with the Console for the schema events
• check with https://stream.wikimedia.org/v2/ui/#/
• check on Test Kitchen (or https://superset.wikimedia.org/sqllab/ )

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