Introduce users to verify via code quality template walkthrough

Hypothesis

We've seen that walking users through a simple example can lead to an increase in adoption of verify. That said, our example does not speak to anything valuable for the user. We believe that providing a walkthrough of the feature set of pipelines while providing the user direct value will lead to more and longer term adoption of Verify.

Experiment design

In this experiment, we'll enroll new namespaces (new signups) in either control or experiment cohorts. We'll then track the Verify adoption (pipeline usage) in both the control and experiment groups. This experiment should be recorded in the experiments users table with a unique experiment_id.

Control

In the control new namespaces will get the current Verify onboarding experience.

Experiment - variant: In the experiment, new namespaces will be directed to an onboarding template with Code Quality report pre-configured. Several simple terms should be explained to the user (e.g. stage) The user should then be directed to the pipelines page and shown the how to determine if a pipeline is complete. The user should then be shown the pipeline logs for code quality report. Finally when the pipeline is complete the user should be directed their code quality report.

Page design: TBD

Experiment tracking

In order to track the success of this experiment, we will enroll new signups (namespaces) into either the control or experiment group, tracked in the experiments_users table with a unique experiment_id. We will enroll 50% of traffic into the control, 50% in experiment

In the experiment cohort, we'll also want to add events for:

• Viewing the pipeline status page
• Viewing pipeline logs page
• Viewing code quality report