Let's add an 'Add to experiment store' action that creates an entry in the experiment store as if the client had been enrolled in some slug/branch, to assist in testing with 'required/excluded' dependencies in sequences of experiments. Currently QA does this by directly manipulating the experiment store but this can be flaky/inconsistent and make it difficult to test sequences of experiments.
Let's add an 'Add to experiment store' action that creates an entry in the experiment store as if the client had been enrolled in some slug/branch, to assist in testing with 'required/excluded' dependencies in sequences of experiments. Currently QA does this by directly manipulating the experiment store but this can be flaky/inconsistent and make it difficult to test sequences of experiments.