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

Convert default experience into a regular one

    Details

      Description

      Acceptance Criteria

      1. The functionality of creating, editing, deleting, duplicating and prioritizing Experiences should remain exactly as they were prior to this change. 
        • A user must be able to create a new Experience. 
        • A user must be able to assign an existing segment to a new Experience. 
        • A  user must be able to create a new segment when creating a new Experience. 
        • A user must be able to edit an existing Experience. 
        • A user must be able to delete an Experience. 
        • A user must be able to duplicate an Experience. 
        • A user must be able to prioritize their Experiences.
        • A user must be able to preview their Experiences. 
      2. The behavior of Default Experiences should remain exactly as they were prior to this change.
        • A user must not be able to edit, delete, duplicate or prioritize the Default Experience. 
      3. Visitors to the page must view the proper Experience according to the segment they belong to. 
        • A visitor who belongs to a single segment must view the Experience associated with that segment. 
        • A visitor who belongs to multiple segments must view the Experience with the highest priority. 
        • A visitor who does not belong to any segment must view the Default Experience. 
      4. The functionality of creating, editing and deleting AB Tests should remain exactly as they were prior to this change. 
        • A user must be able to create a Bounce Rate AB Test. 
        • A user must be able to create a Click AB Test. 
        • A user must be able to create Variants in an AB Test.
        • A user must be able to edit an AB Test. 
        • A user must be able to delete a draft AB Test. 
        • A user must be able to Terminate an AB Test that is in progress. 

      Testing Scenarios

      Acceptance Criteria
       
      Testing Scenarios
       
      Test Strategy
       
      Covered by frontend test? (Yes/No)
       
      Covered by backend test? (Yes/No)
       
      Impedibug Coverage
      • Given there are several users segmented, one per segment
      • And there experiences created in a content page, one per user/segment
      • And the experiences are all over the default experience
      • When each user visits the content page
      • Then the user will see the correct experience
      High  No  No

        Attachments

          Issue Links

          1.
          Test Scenarios Coverage | Test Creation LPS-147448 Technical Testing Closed Carlos Brichete Báez  
          2.
          Improve SegmentsExperience and LayoutPageTemplateStructure services to accept custom SegmentsExperienceKey LPS-147478 Technical Task Closed Eudaldo Alonso  
          3.
          When we are creating a content page creates the necessary entities LPS-148420 Technical Task Closed Eudaldo Alonso  
          4.
          Removes default values from Action and Render commands on Content Page Editor LPS-148540 Technical Task Closed Eudaldo Alonso  
          5.
          Improve SegmentsExperience API to accept userId and groupId LPS-149174 Technical Task Closed Brian Chan  
          6.
          Prepare content page editor to consider default experience as a normal experience LPS-149199 Technical Task Closed Eudaldo Alonso  
          7.
          Adds new method on SegmentsExperience service to get the default segments experience of a Layout LPS-149311 Technical Task Closed Product Team Tango  
          8.
          Convert default experience into a regular one LPS-149434 Technical Task Closed Product Team Tango  
          9.
          Removes deprecated methods on segments-api and segments-service LPS-149459 Technical Task Closed Product Team Tango  
          10.
          Adds new method on LayoutPageTemplateStructureImpl to get the default segments experience data LPS-150306 Technical Task Closed Brian Chan  
          11.
          Encapsulate logic to getSegmentsExperienceId from request on a new util class LPS-150314 Technical Task Closed Product Team Tango  
          12.
          Adds new method to encapsulate the logic of default segments experience creation LPS-150315 Technical Task Closed Product Team Tango  
          13.
          Experiences are not shown correctly LPS-152366 Impedibug Closed Product Team Tango  
          14.
          Test Scenarios Coverage | Backend LPS-152806 Technical Testing Closed Support QA  
          15.
          Test Scenarios Coverage | Frontend LPS-152807 Technical Testing Closed Support QA  
          16.
          Product QA | Test Validation - Round 1 LPS-152808 Technical Testing Closed Carlos Brichete Báez  
          17.
          Product QA | UX Validation - Round 1 LPS-152809 Technical Testing Closed Susana Vázquez  
          18.
          Tests Automation LPS-152810 Technical Testing Closed Carlos Brichete Báez  

            Activity

              People

              Assignee:
              carlos.brichete Carlos Brichete Báez
              Reporter:
              julia.molano Julia Molano
              Engineering Assignee:
              Eudaldo Alonso
              Recent user:
              David Gutiérrez Mesa
              Participants of an Issue:
              Backend Developer(s) Assigned:
              Eudaldo Alonso
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master