Details
-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Add-Ons 35, Add-Ons 36, Add-Ons 37
-
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
Checklists
Acceptance criteria
Attachments
Issue Links
- depends upon
-
ABTEST-157 Research what would be the best way to handle variants and original node
-
- Closed
-
-
ABTEST-171 Lock the original page node when the user adds the first variant to the test
-
- Closed
-