[ABTEST-157] Research what would be the best way to handle variants and original node Created: 03/Mar/20  Updated: 01/Apr/20  Resolved: 30/Mar/20

Status: Closed
Project: A/B Testing
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Story Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Andrei Ichimescu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by ABTEST-140 Create Variant A (original) on test s... Closed
is depended upon by ABTEST-152 Reserve Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Tests generation
Sprint: Add-Ons 34
Story Points: 5

 Description   

Open questions

  • Should we automatically generate variants when the original page has been selected?
    • How the behaviour should be when one selects another original page?
  • When an original page has existing variants, what will happen?
    • Will we show them?

Agreed on the `Simple and more user friendly` variant:

  • Automatically generate an original variant when test starts. (ABTEST-140)
    • Consistency check on the run action whether , there must be a ticket for that somewhere (ABTEST-141)
  • We don’t create a variant automatically, user is in full charge/control over it.
  • What about locking the node when it is in the test setup (without starting?) (ABTEST-171)
    • This way, we don’t have the must to check consistency of the original node over time. (potential changes and stale variants)
  • When someone changes the original page (from the selector), what is the fate of the redundant variants? (ABTEST-140)
    • We keep the variants until the test has been finally started. (then we collect/remove the stale ones)
    • Remove the variants once only the test has started and we know for sure the variants are generated from that test
  • When an original page has existing variants (personalisation), what will happen?
    • It is not part of MVP but ticketed
    • Ignore the variants for the time being

Generated at Sun Feb 11 22:53:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.