Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-99363

As a marketer, I can publish a variant as experience

    Details

    • Sprint:
      TANGO | SP_18 | Aug21-Sep04, TANGO| SP_19 | Sep04-Sep18, TANGO| SP_20 | Sep18-Oct02

      Description

      Motivation

      See Epic (LPS-87072) and Spike (LPS-95354) for general AB testing motivation.

      The purpose of an AB test is to find the page experience that maximizes a goal for a given audience, by comparing the performance of different experience variants during a time. 

      Once the test has a result, the user must take a final manual action. If the test has a winner declared, the user can publish the winner or discard the test; if the test has no winner, the user can only discard the test. 

      Scope

      This story covers the “Publish Winner as Experience” and “Discard Test” actions.

      Design

      • See Figma for reference (see the test-status tab)

      Acceptance Criteria

      1. When a winner is declared for the test, the AB test panel shows the right information

      • Given a test is in winner declared status
      • When the AB test panel is open for that test
      • Then the winner variant is highlighted and both the  “Publish Winner as Experience” and “Discard Test” buttons are shown
      • Then the winner variant is highlighted, and
        • the Publish button is shown on this variant (primary style)
        • the Publish button is shown on all other variants (secondary style) except for control
        • the discard button is available and the bottom.

      2. When no winner is declared for the test, the AB test panel shows the right information

      • Given a test is in no winner status
      • When the AB test panel is open for that test
      • No variant is highlighted and only the “Discard Test” button is shown
      • Then no variant is highlighted and
        • the Publish button is shown (secondary style) on all variants (except for Control)
        • the discard button is available and the bottom.

      3. When “Publish” is clicked, the test is completed

      • Given the test is in winner status
      • When the “Publish” button is clicked on any variant
      • Then the test changes to “Complete” status and
      • The test experience has been replaced with the new experience
      • The Add test button is available again, to add a new test for that experience
        • For now, the test remains in status complete, and it must be deleted to add a new test. This will change once the test history panel is available (see LPS-98829)

      4. When “Discard test” is clicked, the test is terminated

      • Given the test is in winner /no winner status
      • When the “Discard Test” is clicked
      • Then the test changes to “Terminated” "Completed" status and
      • The test experience has not been replaced with the new experience
      • The Add test button is available again, to add a new test for that experience

      5. Publish Winner Experience/Discard test operations in DXP are reflected in AC

      • Given the test is in winner /no winner status
      • When the “Publish Winner as Experience”/”Discard Test” actions are executed in DXP
      • Then the result is reflected in AC

      6. Publish Winner Experience/Discard test operations can be performed from AC

      • Given the test is in winner /no winner status
      • When the “Publish Winner as Experience”/”Discard Test” actions are executed in AC
      • Then the result is reflected in DXP (view previous acceptance criteria)

      Technical Aspects

      In the service layer, the Publish/Discard operations only involve updating the status to Complete/Terminated. Since AC has provided the winner variant to DXP as part of LPS-96787, when the transition is from Winner Declared to Complete, the current control experience of the test must be replaced with the winner variant experience. 

      This involves setting the winner experience to active, and removing the old experience. As a result, the test and all its info will be removed from DXP (unless we defined the opposite). See LPS-99421 for more details.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              manoel.cyreno Manoel Cyreno
              Reporter:
              eduardo.garcia Eduardo García
              Engineering Assignee:
              Eduardo García
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.2.X
                  Master