Closed kingo55 closed 4 years ago
This will also be great as primer to understand how testing platforms work in general. Let's hash this out sometime.
Nice one.
I would just add another term to describe "preview mode" to clarify it's status against "Check: Test state is 'live'" (could be a little confusing).
Maybe "forced into recipe (preview mode)".
Also, should "Check: Test state is 'live'" be earlier on in the flow, i.e. above "Check: Previously bucketed?".
We wouldn't activate a test for a previously bucketed user if the test wasn't live in the first place.
Cool - just updated this with some clearer wording around preview mode
.
I think we might allow previously bucketed users to enter a test if it was in staging mode. Otherwise staging mode wouldn't persist (it's not like users would find themselves in staging mode, because it writes a staging-mode cookie - can only get that if you force your way in):
if (this.options.state.toLowerCase() == OBJECT_STATES.STAGING)
{
cookieName = cookieName + '-staging';
}
The updated flow chart:
This looks great, thanks @kingo55
I think we should document the order of execution in a flowchart, like with MermaidJS:
https://mermaidjs.github.io/#/
This should give users an idea about how test objects are activated, subjects are bucketed etc.