[ABTEST-140] Create Variant A (original) on test start based on originalPage value Created: 03/Feb/20  Updated: 14/May/20  Resolved: 17/Apr/20

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

Type: Story Priority: Neutral
Reporter: Trung Luu Assignee: Andrei Ichimescu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3h
Original Estimate: Not Specified

Issue Links:
dependency
depends upon ABTEST-157 Research what would be the best way t... Closed
depends upon ABTEST-171 Lock the original page node when the ... 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: ABTEST MVP
Sprint: Add-Ons 35, Add-Ons 36, Add-Ons 37
Story Points: 8

 Description   

As per mockup, we will create 2 variants by default based on originalPage value as below

https://preview.uxpin.com/6d073bb3a8ea49f4d1f820f5bc47c39ad3b73e1d#/pages/116232198/simulate/sitemap

AC:
1. When create new test 

  • Need to select originalPage value in Setup tab (required or not?)
  • Display only the variants per default when click to Variants tab (when the test is not started )
  • Able to add more variants
  • Save variants items in JCR if click to 'Save' button

2. When edit test, if originalPage value in Setup tab changes

  • Previous variants items will become invalid
    + A1: Show warning message when changing originalPage and need to add new variants items manually.
    + A2: Remove the invalid variants once only the test has started and we know for sure the variants are generated from that test 
    • Not needed, as the invalid(obsolete variants) are children of the testNode, and deleting the testNode will delete the variants.
    • Check the availability of the DeleteTestAction: delete a test only if its state is (not_started, aborted, completed)

3. When running a test

  • Validate that there is at least one variant created by the user
  • Create the original variant and name it "variant A"
  • When editing a running test, display the original and variants when click to Variants tab 

Notes:

  • 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:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.