Affects Version/s: None
Component/s: Content Page Experience Personalization
Branch Version/s:7.3.x, 7.2.x
Backported to Branch:Committed
Sprint:TANGO | #52 DEV | Jan12-Jan22
Git Pull Request:
Content Pages were introduced in 7.1, and designed to work well with local and remote staging. However, they're not compatible with the Page Versioning feature of Staging.
Page Variations were introduced in Liferay Portal 6.x to support several site administrators working on more than one variation of a page (or group of pages) to be published at different times in the future. The feature can be optionally enabled when staging is enabled. In addition to variations per page, it’s also possible to create “Page Set variations”, which support additions or deletions of pages that also affect one “Page Set variation” and not the others.
Due to a UI bug (
LPS-120839), the staging bar on content pages included options related to page variations even for content pages. This made that several customers assumed that Content Pages had support for page variations, so a solution for this non-existing feature is needed.
- "Anyone" Audience:
- When creating a new experience, the default selected audience will be "Anyone", and it won't be required to select a different one to create the experience
- New experiences created for "anyone" will be placed always below the Default one, in the last position.
- For the rest of experiences targeting different audiences, when creating new ones they will be placed also in the last position of the list, always below the default experience and set as "not-active" as long as they remain below of an Anyone-targeted experience.
- All experiences can be reordered up and down regardless of the default experience.
- "Active" label:
- In cases where several experiences are targeted to the same audience, the one placed above will be indicated with a label "Active". In case there is an Anyone-targeted experience above them, however, they will remain inactive even if they're the highest positioned for their audience. That is to say that all experiences below an Anyone-targeted experience won't be active.
- AB Tests can be run on any experience, even if it's not the active one (current behavior)
- In case there's a AB Test running on one experience, it won't be possible to reorder it, but the rest can be moved up and down normally (current behavior)
- Given a content page
- When the user wants to create a new experience
- Then the default value for the Audience will be "Anyone", although she can select another segment or create a new one
- Given a new experience
- When it is shown in the experiences modal
- Then it is always placed in the last position of the list, always below the default experience and always set as non-active
- Given two different experiences for the same segment
- Then the one placed in a higher position will be indicated as "Active" unless there's an Anyone-targeted experience in a higher position
- Given two different experiences for the segment "Anyone"
- When a user that doesn't belong to any segment lands on the page
- Then the experience indicated as "Active" shows
- Given any experience
- When the user clicks on the "up" and "down" arrow icons
- Then the experience moves up and down the list
- Given any experience which is not active
- When the user reorders the list so it becomes the one placed in the higher position targeting a given segment
- Then the Active label disappears from where it was and appears in the active experience, unless there's an Anyone-targeted experience in a higher position
|AC ID||Test Strategy||Test Scenarios||Is it covered by FrontEnd ? (JS-Unit)||Is it covered by BackEnd? (unit or integration)||Poshi?|
|01||Low||When the user clicks on "New experience" button, the default value for the Audience will be "Anyone"||NO|
|02||Critical||When the user creates a new experience, it is always placed in the last position of the list, always below the default experience and always set as non-active||NO|
|03||High||When the user reorders a experience that was not active and put it in the higher position for that given segment and there's no an Anyone-targeted experience in a higher position, this experience is labeled as active and the experience that was in the higher position before loses the active label||NO|
|04||Low||When there are two or more experiences for the same segment, the one placed in a higher position will be indicated as "Active" unless there's an Anyone-targeted experience in a higher position||NO|
|05||High||When there are two experiences for the segmente "Anyone" and a user that does not belongs to any segment lands on the page, the experience indicated as "Active" shows||NO|
|06||Low||When the user clicks on the up arrow icon of any experience, the experience moves up on the list||YES|
|07||Low||When the user clicks on the down arrow icon of any experience, the experience moves down on the list||YES|
|08||Medium||When a user, that belongs to two or more different segments with experiences for them and these experiences are above the all other Anyone-targeted experiences, lands on the page, the experience with the higher position will be shown||NO|
|09||Medium||When a user, that belongs to two or more different segments with experiences for them and these experiences are below of any other Anyone-targeted experience, lands on the page, the Anyone-targeted experience labeled as active will be shown||NO|
|Test Scenarios Coverage | Test Creation||LPS-125911||Closed|
|Test Scenarios Coverage | Backend||LPS-125912||Closed|
|Test Scenarios Coverage | Frontend||LPS-125913||Closed|
|Product QA | Test Validation - Round 1||LPS-126203||Closed|
|Product QA | UX Validation - Round 1||LPS-126204||Closed|