LPS-138166 - SPIKE - Frontend performance tests for the tree filter (Subtype and Mime Type)

[beltranrengifo]

Jira issue
Spike documentation in Confluence

Motivation

As explained in the links above, this spike tries to document the performance of the tree component used in the Content Dashboard (view epic)

How to reproduce

To reproduce the tests used during the spike

• Checkout to this pull request
• Import to the Documents & Media library the fake data JSON files
• Visit the Content Dashboard app
• Click on Filter and Order
• Click on Type
• Data will show up in a modal: Inspect the modal element
• Find the modal-body div element
• Find the iframe element
• Open in a new tab the iframe's src attribute

You can see now the bare component, ready for evaluation and profiling.

How to change the dataset

• In SelectTypeAndSubtype.js component please find SELECTED_MOCK constant
• Change its value to any of the following
  • xs
  • sm
  • md
  • lg
  • xl
  • xxl

This values refer to keys of the object mocks. You can add new values/mocks to this object if needed.

[liferay-continuous-integration]

Please only forward necessary changes to Brian Chan during stabilization. Nonurgent changes should wait until the ongoing DXP 7.4 GA1 and Portal 7.4 GA4 release has been completed. For more details on the release timeline and status, see product-delivery.

[liferay-continuous-integration]

To conserve resources, the PR Tester does not automatically run for every pull.

If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed.

If your pull was never tested, comment "ci:test" to run the PR Tester for this pull.

[beltranrengifo]

ci:close