Details

    • Type: Testing
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Context

      As we already know all the information that we need to start to investigate the epic, please...

      1. Investigate the epic following this spreadsheet
        1. Remember it is one template, so feel free to add more questions/information, remove unnecessary questions/information
      2. Debate/ask questions to the team about your doubts about how to test this epic
      3. Create Test scenarios / test cases
      4. Tell for the team review to check if we need to add more test

       

      Output

      Our table with the Test scenarios / test cases to be validated in the validation phase.

      to this table, follow the example that we have in this ticket - LPS-121721.

       

      Test Information section

      **
      Test Scenarios:

      Requirement Test Case Covered by frontend/backend unit test? (Yes/No) Test Priority (business impact)
      Update sass build processes to use a JS-based solution like Dart Sass Given PR
      When run ci:test:relevant
      Then all tests pass or resolved as unrelated
      no 4-major
      Deprecate the legacy Java tasks and classes Given a terminal at portal root
      When run `find -not -path "./modules/sdk*" | grep 'CSSBuilder.java|CSSRTLConverter.java|BuildCSSTask.java'`
      Then no lines are returned
      no 3-medium
      Provide RTL conversion support from liferay-npm-scripts Given portal page
      When change language to arabic
      Then RTL layout is applied to page
      no 5-critical

      Exploratory testing to consider:

      Test Scenarios Covered by frontend/backend Unit Test? Test Priority (business impact)
      Exploratory smoke testing. Widely used areas of portal look ok: Sign in, home page, control panel, add page, add a portlet and content. no 4-major
      Exploratory smoke testing on supported browsers (FF / Chrome / Edge / Safari desktop) no 2-low
      Exploratory test to see if there's common sass compilation errors that make sense no 2-low

      Performance testing to consider:

      Test Scenarios Covered by frontend/backend Unit Test? Test Priority (business impact)
      Exploratory to compare build times before and after the update. Run `gw buildCSS` on /modules after `gw yarnInstall` no 2-low

        Attachments

          Activity

            People

            Assignee:
            john.co John Co
            Reporter:
            manoel.cyreno Manoel Cyreno
            Recent user:
            John Co
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package