Convert default experience into a regular one

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Content Page Experience Personalization
• Labels:
  • d_22_02
  • echo-board-in
  • echo-not-test-scope
  • fc_22_02
  • fc_22_03
  • fc_22_04
  • fc_22_05
  • no-ff
• Epic Link: As a site admin, I want to have different content page variations per Site Variation
• Sprint: TANGO | #76 DEV | Apr18-May09, TANGO | #77 DEV | May09-Jun06
• Git Pull Request: https://github.com/liferay-tango/liferay-portal/pull/2334

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