Create a poshi test to cover LPS-108566

• Type: Testing
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Product Menu
• Labels: None
• Epic Link: 7.3 CE GA6 / DXP Testing tasks
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/92848, https://github.com/brianchandotcom/liferay-portal/pull/92885
• QA Test Name:
  • LocalFile.FragmentsEditor#AutocompleteFragmentWithCollectionResource
• QA Test Score: 5

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

The focus of this task is to implement the CRITICAL, HIGH and MID tests of the related story, but if you believe that can and have time to implement the LOW and TRIVIAL test cases, please, create one more subtask to it, and go ahead!

 

Test Scenarios

Test Scenarios	Test Strategy	Kind of test	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd ? (unit or integration)
When type ${ in HTML section, the IntelliSense containing available variables popups and Auto-Complete works	Smoke	Manual	No	No
When type [@ in HTML section, the IntelliSense containing available taglibs popups and Auto-Complete works	Smoke	Manual	No	No
When type [resources: in HTML section of fragment, the IntelliSense containing available resources only from current collection popups and Auto-Complete works	Smoke	Manual	No	No
If current collection doesn't has resources, when type [resources: in HTML section of fragment, the IntelliSense won't popup	Sanity	Manual	No	No

Test Cases

Case 1:
When type ${ in HTML section, the IntelliSense containing available variables popups and Auto-Complete works

1. Site Builder > Page Fragments
2. Add a new collection
3. Add a new fragment
4. Type ${ in HTML section
5. Assert the IntelliSense containing available variables popups
6. Click portalUtil
7. Assert ${portalUtil is shown in section

Case 2:
When type [@ in HTML section, the IntelliSense containing available taglibs popups and Auto-Complete works

1. Site Builder > Page Fragments
2. Add a new collection
3. Add a new fragment
4. Type [@ in HTML section
5. Assert the IntelliSense containing available taglibs popups
6. Click liferay_editor
7. Assert [@liferay_editor is shown in section

Case 3:
When type [resources: in HTML section of fragment, the IntelliSense containing available resources only from current collection popups and Auto-Complete works

1. Site Builder > Page Fragments
2. Add the first collection
3. Resources tab
4. Upload Document_1.jpg as resource
5. Add the second collection
6. Resources tab
7. Upload Document_2.jpg as resource
8. Fragment tab
9. Add a new fragment in the second collection
10. Type [resources: in HTML section
11. Assert the IntelliSense containing only Document_2.jpg popups
12. Click Document_2.jpg
13. Assert [resources:Document_2.jpg is shown in section

Case 4:
If current collection doesn't has resources, when type [resources: in HTML section of fragment, the IntelliSense won't popup

1. Site Builder > Page Fragments
2. Add a new collection
3. Add a new fragment
4. Type [resources: in HTML section
5. Assert the IntelliSense doesn't popup