Details

    • Testing
    • Status: Closed
    • Minor
    • Resolution: Completed
    • None
    • None
    • Metal.js
    • 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

       

      Requirement Test Scenarios Covered by frontend/backend unit test? (Yes/No) Test Priority (business impact)
      There should be no dependencies with any metal module in any other module in their package.json file  Given console terminal at liferay portal root
      When run command:
      git grep -W metal -- '*package.json'

      Then returns no lines except from frontend-js-metal-web directory if any

      no 5-critical
      There are no usages of any metal modules in DXP's code base Given console terminal at liferay portal root
      When run command:
      git grep -W metal

      Then returns no lines except from frontend-js-metal-web directory if any

      no 4-major
      There are no usages of any metal modules in DXP's code base  Given console terminal at liferay portal root
      When run command:
      git grep -W "import {[A-Za-z]*\} from 'metal'\|import [A-Za-z]* from 'metal'" *

      Then returns no lines except from frontend-js-metal-web directory if any

      no 3-medium
      LPS-125185 - There is no references to any any metal module in any .npmbundlerrc file Given console terminal at liferay portal root
      When run command:
       git grep -E '"metal|incremental-dom-string' -- '*.npmbundlerrc' ':(exclude)*frontend-js-metal-web*'

      Then returns no lines except from frontend-js-metal-web directory if any

      no 4-major
      LPS-125174 - The metal eslintrc preset is not used in the DXP codebase Given console terminal at liferay portal root
      When run command:
      git grep -W @liferay/eslint-config/metal -- '*.eslintrc.js'

      Then returns no lines except from frontend-js-metal-web directory if any

      no 4-major
      For backwards compatibility, all metal modules should still be bundled as part of frontend-js-metal-web  Given   https://github.com/liferay/liferay-portal/blob/db5efa19792bebefbdfe1c8022b84469bbf73942/modules/apps/frontend-js/frontend-js-metal-web/package.json
      When I check the history from 8th January and compare with the current
      Then files are the same
       no  4-major

      Attachments

        Activity

          People

            pawel.grabowski Pawel Grabowski (Inactive)
            john.co John Co
            Kiyoshi Lee Kiyoshi Lee
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Packages

                Version Package