Details
-
Epic
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
-
None
Description
Test Scenarios:
| Requirement | Test Scenarios | Covered by frontend/backend Unit Test? | Test Priority (business impact) | Chrome Pass/Fail |
|---|---|---|---|---|
| Given: Remote Apps admin page When: Click Add Button And When: Input Name: Vanilla Counter Type: Custom Element HTML Element Name: vanilla-counter URL: http://remote-component-test.wincent.com/packages/vanilla-counter/index.js And When: Save Then: Custom Elements admin page lists the Name and Type |
no | 5-critical | ||
| Given: Remote Apps admin page When: Click Add Button And When: Input Name: Vanilla Counter Type: Custom Element HTML Element Name: vanilla-counter Instanceable: toggled on Properties: test-data-user=QAuser CSS URL: http://remote-component-test.wincent.com/index.css And When: Save Then: The listed Name matches the edit And When: Click Portlet Name Then: All fields of Remote App are saved properly |
no | 5-critical | ||
| Given: A created Custom Remote App admin page When: Click Edit And When: Edit Name, HTML Element Name, Instanceable, Properties tag, CSS URL And When: Save Then: The Widget fields are updated on the admin page And When: Click Edit Then: The Widget fields are updated |
no | 4-major | ||
| Given: A created Custom Remote App When: Click Delete Then: The Custom Element Widget is removed from Custom Elements admin page |
no | 4-major | ||
| Given: A created Custom Element Widget referencing vanilla counter custom element (http://remote-component-test.wincent.com/packages/vanilla-counter/index.js) And Given: Custom Element Widget on content page When: Navigate to content page Then: Plus and minus buttons are present in portlet And When: Clicking on plus button Then: Adds 1 to counter And When: Clicking on minus button Then: Subtracts 1 to counter |
no | 5-critical | ||
| Given: A created Custom Element Widget referencing vanilla counter custom element (http://remote-component-test.wincent.com/packages/vanilla-counter/index.js) And Given: Custom Element Widget on content page When: Open Add Widget Panel Then: Able to add another Custom Element Widget to the page |
no | 3-medium | ||
| Given: A created Custom Element Widget referencing vanilla counter custom element (http://remote-component-test.wincent.com/packages/vanilla-counter/index.js) And Given: Properties: test-data-user=QAuser And Given: Custom Element Widget on content page When: Navigate to content page Then: test-data-user=QAuser element is present in html |
no | 3-medium | ||
| Given: A created Custom Element Widget referencing vanilla counter custom element (http://remote-component-test.wincent.com/packages/vanilla-counter/index.js) And Given: CSS URLs: http://remote-component-test.wincent.com/index.css And Given: Custom Element Widget on content page When: Navigate to content page Then: in DOM > Sources > remote-component-test.wincent.com/index.css is listed and contents match ``` body { display: flex; flex-direction: column; font-family: sans-serif; margin: 0; min-height: 100vh; } footer { background-color: peach-puff; border-top: 1px solid #ccc; padding: 16px; } header { background-color: azure; border-bottom: 1px solid #ccc; } li { line-height: 1.5; margin-bottom: 1em; } #content { flex: 1; padding: 16px; } ``` |
no | 3-medium | ||
| Given: A created Custom Element Widget referencing vanilla counter custom element (http://remote-component-test.wincent.com/packages/vanilla-counter/index.js) on a previous liferay version And Given: Custom Element Widget on content page When: Upgrade liferay version to latest version Then: All fields are present And Then: Plus and minus buttons are present in portlet And When: Clicking on plus button Then: Adds 1 to counter And When: Clicking on minus button Then: Subtracts 1 to counter |
no | 3-medium | ||
| |
Given: Remote Apps Add page When: Type is IFrame Then: HTML Element Name and CSS URL fields are not present When: select type Custom Element Then: HTML Element Name and CSS URL fields are present |
no | 4-major | |
| |
Given: Remote Apps add page When: click on Portlet Category field/dropdown Then: Options for basic portlet categories are displayed (Collaboration, Sample, Remote Apps, Wiki, among others) And when: select Collaboration And when: go to widget/content page And when: search for the created remote app in add widget Then: widget portlet is categorized under Collaboration category |
no | 3-medium | |
| Given: Remote App When: change the portlet alias Then: the portlet alias is reflected on the remote app in the add widget panel |
no | 3-medium | ||
| Given: Remote App of type Custom Element When: has two URLs and two CSS URLs And When: edit the app Then: all fields are present |
no | 4-major | ||
| Given: Remote App of type Custom Element When: has two URLs and two CSS URLs And When: Add remote app to page Then: only the component with associated element name is displayed (ie: setting vanilla-counter as element name displays only vanilla counter js portlet) And then: both CSS URLs are present in source tab |
no | 4-major | ||
| Given: Remote app created And Given: Remote app portlet on widget page When: Create new virtual instance company And When: Navigate to virtual instance widget page Then: The remote app portlet is not present on the page And Then: The remote app portlet is not available on add widget panel And When: Navigate to Remote Apps admin Then: Remote app display list is empty |
yes - LRQA-70244 | 4-major | ||
| Given: Remote app created And Given: Remote app portlet on widget page When: Navigate to portlet ellipsis > Configuration And When: Click on Sharing tab And When: Copy the URL pointed by the <iframe> And When: modify to URL to use localhostB instead Then: the remote app portlet is not present |
yes - LRQA-70244 | 4-major |
Exploratory testing to consider:
| Test Scenarios | Covered by frontend/backend Unit Test? | Test Priority (business impact) | Firefox Pass/Fail |
Chrome Pass/Fail |
Safari Pass/Fail | Edge Pass/Fail |
|---|---|---|---|---|---|---|
| Exploratory test for visual and functional issues on Chrome/FF/Edge/Safari. 1. Check that the admin pages are displays properly 2. Validate custom element widget is displayed properly |
no | 2-low | n/a | |||
| Exploratory test for edge cases: Some items to explore: 1. What happens with multiple custom elements that are defined with the same html tag? 2. Will a different host location still work? ie: js file on google drive |
no | 2-low | n/a | n/a | n/a | |
| Given: Remote App edit pages When: Use keyboard only Then: Able to access all interactible elements involved |
no | 2-low | n/a | n/a | n/a | |
| Given: Custom Elements and Custom Elements Widget admin and edit pages When: Use AXE chrome extension Then: No issues related to WCAG AA and A |
no | 2-low | n/a | n/a | n/a |