-
Notifications
You must be signed in to change notification settings - Fork 30
Set up product element 0% test #14876
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hello 👋! When you're ready to run Chromatic, please apply the You will need to reapply the label each time you want to run Chromatic. |
charleycampbell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me! Also great updates to the docs and code comments!
|
Seen on PROD (merged by @emma-imber 8 minutes and 59 seconds ago) Please check your changes! |
What does this change?
Adds a 0% test to measure the impact of the Product Element on click through rate. Also makes some changes to the ab testing docs to update the example test name being used to be kebab case, to make it clearer to future users.
Why?
We want to test the impact of the Product Element on click through rate using a 'hold back' test. The audience in the control will see the Product Element as it was designed, the same as anyone not in the test. The audience in the variant will see the Product Element rendered without the additional left col or inline product cards. This is to mock a page experience very close to that of pages without the Product Element. We then want to measure the difference in click through rate between the control and variant to see if there's a measurable benefit to the new Product Element designs.
We're setting this test up as a 0% test to start so that we can check that the test data is coming through correctly.
Screenshots
Desktop
Mobile