Details

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

      Description

      Context
      Execute the tests of the epic LPS-122900, use the information in the Test Information section to perform the tests.

      Output
      Tell in one comment (in the epic ticket) the final status of this first round, and in this ticket, fill the bug section into this ticket.
      Remember to link the bug (if you discover) with the Epic ticket.

      *{color:#14892c}PASSED{color}* / *{color:#d04437}FAILED{color}* / *{color:#59afe1}BLOCKED{color}* Manual Testing following the steps in the description.
      
      *Verified on:*
      *Environment*: localhost
      *Github*: https://github.com/liferay/liferay-portal.git
      *Branch*: master
      *Bundle*: Liferay CE
      *Database*: MySQL 5.7.22
      *Last Commit*: ? 
      
      || Test Scenarios || Test Result ||
      | |*{color:#14892c}PASSED{color}* / *{color:#d04437}FAILED{color}* / *{color:#59afe1}BLOCKED{color}*|
      | |*{color:#14892c}PASSED{color}* / *{color:#d04437}FAILED{color}* / *{color:#59afe1}BLOCKED{color}*|
      ...
      

      Bugs:
       - PASS
       - To Do
       - FAIL

      • Impeditive:
        Ticket Title QA Status
        ? ?
      • Not impeditive:
        Ticket Title QA Status
        ? ?

       

      Test Scenarios:

      Requirement Test Case Covered by frontend/backend unit test? (Yes/No) Test Priority (business impact)
      Deprecate the legacy Java tasks and classes Given a terminal at portal root
      When run `find -not -path "./modules/sdk*" | grep 'CSSRTLConverter.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

      other test scenarios already done through task PRs:

      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

        Attachments

          Activity

            People

            Assignee:
            support-lep@liferay.com SE Support
            Reporter:
            john.co John Co
            Recent user:
            Manoel Cyreno
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package