Add 0% editorial-headline-test to test definitions - #16554
Merged
Merged
Conversation
abeddow91
commented
Aug 12, 2026
abeddow91
commented
Aug 12, 2026
…initions. This test is the parent / platform test for ediorial headline ab test. Its responsibility is to manage user bucket participation as well as over all test on/off status, rather than managing individual editorial a/b test lifecycles
abeddow91
force-pushed
the
ab/setup-platform-ab-test
branch
from
August 13, 2026 12:37
0cdf5fa to
d0f6b33
Compare
emma-imber
approved these changes
Aug 13, 2026
|
Seen on PROD (merged by @abeddow91 8 minutes and 48 seconds ago) Please check your changes! |
This was referenced Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
Adds "fronts-and-curation-editorial-headline-test" as a 0% test.
This test is the parent / platform test for Editorial headline A/B tests. Its responsibility is to manage user bucket participation as well as over all the global test on/off status, rather than managing individual editorial a/b test lifecycles which is managed by config in the fronts tool.
This has been set up as a 0% test for testing. Once this feature is ready for production, it will be slowly ramped up to a 50/50 test.
This test framework is being developed by the A/B test mission. As such, there is no long life team to associate with this test. Given that these tests will run on fronts cards only (at least in the immediate), this test has been assoiciated with the
Fronts and Curationteam.How has this change been tested?
Tests
Where applicable please add automated tests.
If you'd like help testing your changes as part of the PR review process then mention that explicitly here.
Automated tests
You can find examples of each type of test in the repo.
Manual testing
-->
Screenshots