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

As a Content Editor I cannot edit the content of an Experience with an active AB Test

    Details

    • Type: Story
    • Status: Ready for QA
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: AB Testing
    • Labels:

      Description

      As a content editor, I want to know the implications of editing content currently being tested so that I don't lose any content changes.

      Motivation

      A user can modify content subject to an ongoing AB Test. This has some implications that the user should know before editing so she does not lose any content changes:

      • The content of the Experience the user edits won't apply to any of the variants tested against it.
      • Any changes that the user apply to the content under this Experience will be lost whenever an alternative is published.
      • Changing the Experience content in the middle of an AB Test can render the test conclusions inaccurate.

      An alternative to inform the user about this is to simply lock the testing Experience edition and force the user to stop the AB Test in order to be able to edit it. 

      Design

      https://www.figma.com/file/V9BLNpuTpebLC6JapradSV/LPS-103334-feedback-not-edit-Experience-with-active-AB-Test?node-id=0%3A1
      (Design does not have definitive copy, however the full width warning is the tone to inform about it).

      Figma: https://www.figma.com/file/t95V3oSshIV148ErDQtxzC/lps-101341-experiences-affected-by-active-tests?node-id=1%3A61
      Note: if the final solution ends to be using the alert to warn the user, he alert style should be warning.

      Acceptance Criteria

      Glossary:

      Active AB Test: AB Test in running/winner declared/non winner declared

      Page Editor in Non-Edition Mode:

      • The sidebar has edition sections disabled (to be defined Andres Fulla)
      • The Fragments do not show the Floating Toolbar when interacted with
      • The user is informed about the Edition Locking (Susana Vázquez will define this behaviour)

      Page Editor in Edition Mode:

      • The side bar has no sections disabled.
      • The Fragments show the Floating Toolbar when interacted with
      • The user is not informed about Edition Locking

      Given/when/then:

      First render for Default Experience with Active AB Test:

      • Given a Page with a Default Experience associated with an Active AB Test
      • When a user accesses the Page Editor
      • Then the Page Editor is in Non-Edition Mode

      First render for Default Experience without Active AB Test:

      • Given a Page with a Default Experience not associated with an Active AB Test
      • When a user accesses the Page Editor
      • Then the Page Editor is in Edition Mode

       The user switches to an Experience with an Active AB Test:

      • Given a Page with an Experience named Experience #1
      • When a user accesses the Page Editor and selects the Experience #1
      • Then the Page Editor is in Non-Edition Mode

      The user switches to a Experience without an Active AB Test:

      • Given a Page with an Experience not associated with an Active AB Test and named Experience #2
      • When a user accesses the Page Editor
      • Then the Page Editor is in Edition Mode

      First render for an Experience with Active AB Test:

      • Given a Page with an Experience associated with an Active AB Test and named Experience #2
      • When the user opens the dropdown experiences selector
      • Then the Experience has an icon indicating that the Experience is locked

      Known limitations

      There are known edition tools that affect the whole page. We might be locking them per Experience

      Test Scenarios

      AC ID Test Strategy Test Scenarios Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd ? (unit or integration)
      01 and 03 Smoke Validate if the AB Test is in the status running, the experience about the AB Test is active is in Non-Edition Mode   NO NO
      01 and 03 Sanity Validate if the AB Test is in the status winner declared, the experience about the AB Test is active is in Non-Edition Mode   NO NO
      01 and 03 Regression Validate if the AB Test is in the status no winner declared, the experience about the AB Test is active is in Non-Edition Mode   NO  NO
      02 and 04 Smoke Validate if the AB Test is in the status draft, the experience about the AB Test is active is in Edition Mode   NO  NO
      02 and 04 Sanity Validate if the AB Test is in the status completed, the experience about the AB Test is active is in Edition Mode   NO  NO
      02 and 04 Regression Validate if the AB Test is in the status terminated, the experience about the AB Test is active is in Edition Mode  NO   NO
      05 Smoke Validate if the AB Test is in status locked, the experience is locked YES  N/A

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Packages

                  Version Package