Details

    • Type: Testing
    • Status: In Progress
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Sprint:
      S04E25 - Reflektor, S04E26 - Vulgar Display of Pwr, S04E27 - Oh My My, S04E28 - Bridge over troubl..., S04E29 - Unimagine, S04E30 - Sea Change

      Description

      Create test automation to validate the critical test scenarios/cases of the related story.

      The focus of this task is to implement the CRITICAL and MAJOR tests of the parent epic, but if you believe that can and have time to implement the lower priority tests please, create one more subtask to it, and go ahead! 

      • Create a subtask for each testcase in this ticket (Click More > create subtask > technical testing > title = ${Testcase Name})
      • Assign subtask to yourself
      • Send PR to liferay-frontend, and assign subtask to John for review
      • Close subtask when merged

       

      Requirement Test Case Test Priority (business impact) Testcase Name
      Activation      
      1. Tool can be executed on runtime over a given page
      3. Runs automatically in the background
      Given portal bundle built with nodejs.node.env=development in the build.properties
      When bundle is started
      And open localhost:8080 (landing page)
      Then accessibility panel is present on the page
      5-critical  A11yTool#CanBeEnabled
      1. Tool can be executed on runtime over a given page Given any DXP bundle with nodejs.node.env=development in the build.properties
      And Given bundle is started and portal is loaded
      Whenthe a11y tool is disabled in the system settings  the a11y tool is disabled in com.liferay.frontend.js.a11y.web.internal.configuration.FFA11yConfiguration.config with enable=B"false"
      Then accessibility panel is not present on the page
      5-critical  A11yTool#CanBeDisabledWithDevelopment
      1. Tool can be executed on runtime over a given page Given any DXP bundle built with default build.properties
      When bundle is started and portal is loaded
      And open localhost:8080 (landing page)
      Then accessibility panel is not present on the page
      5-critical  A11yTool#IsDisabledByDefault
      Issues Related to Rule      
      2. Test the page for a given set of accessibility rules Given a11y tool enabled
      When navigate to a page without any a11y violations
      Then side panel will list no violations on the page
      And Then there are no highlight elements present on the page
      And Then there are no icons present on the page
      5-critical  A11yTool#CanDetectNoViolations
        Given a11y tool enabled
      When navigate to a page with an a11y violation
      Then side panel will list violation on the page
      And Then there is a highlighted element present on the page
      And Then there is a highlight icon present on the page
      5-critical A11yTool#CanDetectViolation
      5. Provides additional information about the a11y violations found as hints on how to address them Given a11y tool enabled
      And Given a fragment with a11y violation on a page
      When navigate to the page with a11y violations
      Then a side panel with violation is present on page
      5-critical  A11yTool#ShowsSidePanelWithViolation
      5. Provides additional information about the a11y violations found as hints on how to address them Given when a11y tool enabled
      AndGiven a portal page with the panel in top-level view
      When there are violations on the page
      Then it will show a list of rules being violated sorted by descending impact
      4-major  A11yTool#OrdersViolationsByDescendingImpact
      4. Presents itself as a visual barrier to the experience
      5. Provides additional information about the a11y violations found as hints on how to address them
      Given a11y tool enabled
      And Given a fragment with 3 different a11y violation on a page
      When navigate to the page with a11y violations
      Then all elements that are in a11y violation will be highlighted
      And Then all elements with violation has an icon next to the highlight
      4-major  A11yTool#CanHighlightMultipleViolations
      5. Provides additional information about the a11y violations found as hints on how to address them Given when a11y tool enabled
      And Given a portal page with a rule violation
      When click on a rule in the accessibility panel
      Then accessibility panel contains info of accessibility rule violation:
      1. rule name
      2. impact level
      3. link to Category rule (WCAG)
      And section that show details for the single rule being violated can be viewed
      And occurrences are listed on the accessibility panel
      4-major   A11yTool#CanDisplayViolationRuleDetails
      5. Provides additional information about the a11y violations found as hints on how to address them Given any portal page with a violation and a11y tool is enabled
      When violation icon is clicked
      Then pop up panel should appear
      And Rule name is present in pop up panel
      And Impact/severity indicating how serious the violation is, in a 3 or 4-value scale in pop up panel
      And Brief description of the rule is in pop up panel
      And Link to occurrence accessibility panel is in in pop up panel
      3-medium A11yTool#CanDisplayViolationDetailsInPopUp
      5. Provides additional information about the a11y violations found as hints on how to address them Given any portal page with a violation and a11y tool is enabled
      When violation icon is clicked
      And close button is clicked on pop up
      Then pop up panel should not be present
      3-medium A11yTool#CanViewViolations
      5. Provides additional information about the a11y violations found as hints on how to address them Given a11y violations on a page
      And clicking the icon next to highlighted violation
      When click on a listed rule violation from pop up
      Then the side panel will show the violation occurrence
      4-major A11yTool#CanDisplayViolationDetailsInSidePanel
      5. Provides additional information about the a11y violations found as hints on how to address them Given when a11y tool enabled
      And Given a portal page with a rule violation
      When click on a rule in the accessibility panel
      And click on a occurrence
      Then the correct target and code is displayed on the accessibility panel
      4-major A11yTool#CanDisplayTargetCode
      5. Provides additional information about the a11y violations found as hints on how to address them Given a11y tool enabled and in top-level view
      And Given 2 of the same violations on the page
      And Given 1 different violation on the page
      When click the rule violation in the panel
      Then two occurrences are listed for the same violation
      And the 2 occurrences are highlighted on the page
      And the different violation is not listed nor highlighted
      3-medium  A11yTool#CanDetectMultipleOccurencesOfSameViolations
      5. Provides additional information about the a11y violations found as hints on how to address them Given a11y tool enabled and in top-level view
      And Given 2 of the same violations on the page
      When click the rule violation in the panel
      And click on occurrence 2
      Then the occurrence 2 target and code information is correctly listed
      3-medium A11yTool#CanDisplayTargetCodeOfSecondViolation
      5. Provides additional information about the a11y violations found as hints on how to address them Given when a11y tool enabled
      And Given a portal page with no rule violations
      When a fragment with a rule violation is added to the page
      Then the rule violation will be highlighted and appear on the panel
      4-major  A11yTool#CanDetectViolationInDynamicPage
       Filters      
      5. Provides additional information about the a11y violations found as hints on how to address them Given top-level view of accessibility panel
      When click on filter button
      Then toggles to change impact and category rule are available
      5-critical A11yTool#CanFilterViolationsByImpactAndCategory
      5. Provides additional information about the a11y violations found as hints on how to address them Given when a11y tool enabled
      And the portal page has a "Minor", "Moderate", "Serious", "Critical" set of violations
      When Impact filter is enabled on "Minor", "Moderate", "Serious", "Critical" set of violations
      Then it will show all four violations on the side panel
      And the elements with violation will be highlighted
      And the elements with violation have an icon next to the highlight
      3-medium  A11yTool#CanFilterViolationsByAllImpact
      already covered in another testcase above Given when a11y tool enabled
      And the portal page has a "Minor", "Moderate", "Serious", "Critical" set of violations
      Then accessibility panel will order the violations from most important to less important
      -3-medium-  
      5. Provides additional information about the a11y violations found as hints on how to address them Given when a11y tool enabled
      And the portal page has a "Minor", "Moderate", "Serious", "Critical" set of violations
      When Impact filter is set only for "Critical"
      Then it will show Critical violation on the side panel
      And the no other violations are present on side panel
      And the element with critical violation will be highlighted
      And there are no other highlights on the page
      And the element has an icon next to the highlight
      5-critical  A11yTool#CanFilterViolationsByCriticalImpactOnly
      5. Provides additional information about the a11y violations found as hints on how to address them Given when a11y tool enabled
      And the portal page has a "Minor", "Moderate", "Serious", "Critical" set of violations
      When Impact filters are all turned off
      Then no violations are present on side panel
      And no elements highlights are present on page
      And no icons for violations are present on page
      4-major A11yTool#CanFilterOutAllViolationsByImpact 
      5. Provides additional information about the a11y violations found as hints on how to address them Given top-level view of side panel
      And Given in filter view is open
      When a filter is toggled/changed
      And refresh the page
      And When hover over the same accessibility issue that was toggled
      Then the filter is back to default setting
      2-low  A11yTool#FiltersAreResetToDefaultAfterPageRefresh
       Inspector      
      5. Provides additional information about the a11y violations found as hints on how to address them Given a portal page with a rule violation
      When click on a rule in the accessibility panel
      And click on occurrence 1 in accessibility panel
      When the View In Inspector link is clicked in accessibility panel
      Then browser console will appear in element inspect mode
      And element that is in violation will be highlighted in the console
      3-medium  A11yTool#CanLocateAViolationOnPageByOccurence

       

        Attachments

        1.
        A11yTool#CanBeEnabled LPS-140655 Technical Testing Closed Susan Chen  
        2.
        A11yTool#CanDetectNoViolations LPS-140736 Technical Testing Closed John Co  
        3.
        A11yTool#CanDetectViolation LPS-141327 Technical Testing Closed John Co  
        4.
        A11yTool#ShowsSidePanelWithViolation LPS-141455 Technical Testing Closed Susan Chen  
        5.
        A11yTool#CanFilterViolationsByImpactAndCategory LPS-141734 Technical Testing Closed Susan Chen  
        6.
        A11yTool#CanFilterViolationsByCriticalImpactOnly LPS-141820 Technical Testing Closed Susan Chen  
        7.
        A11yTool#CanBeDisabledWithDevelopment LPS-142107 Technical Testing Closed Susan Chen  
        8.
        A11yTool#IsDisabledByDefault LPS-142249 Technical Testing Closed Susan Chen  
        9.
        A11yTool#OrdersViolationsByDescendingImpact LPS-142271 Technical Testing Closed Susan Chen  
        10.
        A11yTool#CanHighlightMultipleViolations LPS-142318 Technical Testing Closed Susan Chen  
        11.
        A11yTool#CanDisplayViolationRuleDetails LPS-142322 Technical Testing Closed Susan Chen  
        12.
        A11yTool#CanDisplayViolationDetailsInSidePanel LPS-142323 Technical Testing Closed Susan Chen  
        13.
        A11yTool#CanDisplayTargetCode LPS-142324 Technical Testing Closed Susan Chen  
        14.
        A11yTool#CanDetectViolationInDynamicPage LPS-142325 Technical Testing Closed Susan Chen  
        15.
        A11yTool#CanFilterOutAllViolationsByImpact LPS-142326 Technical Testing Closed Susan Chen  
        16.
        A11yTool#CanDisplayViolationDetailsInPopUp LPS-142327 Technical Testing Closed Susan Chen  
        17.
        A11yTool#CanViewViolations LPS-142328 Technical Testing Open Susan Chen  
        18.
        A11yTool#CanDetectMultipleOccurencesOfSameViolations LPS-142329 Technical Testing In Review Summer Zhang  
        19.
        A11yTool#CanDisplayTargetCodeOfSecondViolation LPS-142330 Technical Testing In Progress Susan Chen  
        20.
        A11yTool#CanFilterViolationsByAllImpact LPS-142331 Technical Testing In Progress Bronson Perez  
        21.
        A11yTool#CanLocateAViolationOnPageByOccurence LPS-142332 Technical Testing Closed Bronson Perez  
        22.
        A11yTool#FiltersAreResetToDefaultAfterPageRefresh LPS-142333 Technical Testing In Review Summer Zhang  

          Activity

            People

            Assignee:
            susan.chen Susan Chen
            Reporter:
            john.co John Co
            Recent user:
            Bruno Fernández
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Packages

                Version Package