Test/dev mode
Maxime Dupré (@maximehugodupre)
Thanks for the request Ellis 😊
Let me try to have a deeper understanding of what you're requesting.
> a mode where the cookie doesn't save (to make it easier to see the variants)
So in this mode, you would like that
experiment.version
returns a random version on each page refresh? This way you don't have to keep deleting the cookie until the wanted variant is displayed, but simply refresh the page?> visits/conversions aren't saved to avoid skewing the real test
This makes sense. I wonder if it is not preferable/less confusing to write the code explicitly like this instead:
prod && experiment.trackVisit()
or process.env.NODE_ENV === 'production' && experiment.trackVisit()
(or use an "if" statement instead of the && syntax).Let me know what you think 😁🙏
E
Ellis Crosby
Maxime Dupré (@maximehugodupre): Thanks for getting back! I think what I'm looking for is more some kind of switch in the UI to create a sort of debug mode for a test.
Whenever we release a test we do a lot of QAing that the test + whatever it is we're testing is working - in the current set up this is difficult as 1) our QA testers often have to use an incognito window and keep refreshing until they're in a test group and 2) we often have a lot of irrelevant data tracked to the test before it is properly launched.
Having some kind of debug mode where the data isn't tracked and the experiment cohort changes with each request would help out a tonne here - and then when we're ready to test we can flick it off to start the test
We could disable tests in the app like you mentioned, but then we'd struggle to QA that the ab test is actually working