Details
-
Epic
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
-
None
-
To Do
Description
As part of the analysis of balloon editor needs (LPS-122371), we identified some occurrences of AlloyEditor in commerce and forms products. Given the plans to create a new balloon editor and deprecate AlloyEditor in the future, these occurrences shall be migrated to use a different solution.
Moreover, the identified usages seem not needed: a regular ckeditor or even just a properly formatted input field can be used in place of AlloyEditor.
Goal of this epic is to remove AlloyEditor occurrences in Commerce and Forms, substituting a more suitable solution for those.
Acceptance criteria:
- No usages of AlloyEditor are made by commerce code
- No usages of AlloyEditor are made by forms code
- All usages of AlloyEditor are properly replaced, meaning there's no functionality loss
Test Scenarios:
Requirement | Test Case | Covered by frontend/backend unit test? (Yes/No) | Test Priority (business impact) | Chrome Pass/Fail |
---|---|---|---|---|
No usages of AlloyEditor are made by commerce code | Given a portal site with Speedwell site template When navigate to Global Menu > Commerce > Products And When Edit an existing product And When inspect the Full Description section Then the section is not using alloy editor |
no | 5-critical | |
Given a portal site with Speedwell site template When navigate to Global Menu > Commerce > Products And When Add a new Virtual type Product And When inspect the Terms of Use section under Virtual tab Then the section is not using alloy editor |
no | 3-medium | ||
Given a portal site with Speedwell site template When navigate to Global Menu > Commerce > Channels, select the site type channel And When Edit the Money Order Payment Method, check Active And When inspect the Message section in Configuration page Then the section is not using alloy editor |
no | 3-medium | ||
No usages of AlloyEditor are made by forms code | Given Editing a form When inspect Title and Description Then alloy editor is not present in input element html |
no | 5-critical | |
Given Editing a element set When inspect Title and Description Then alloy editor is not present in input element html |
no | 3-medium | ||
All usages of AlloyEditor are properly replaced, meaning there's no functionality loss | Given Add form/element set When Type into Title and Description fields replaced by Ckeditor Then can submit a new form/element set And Then View saved form/elemment set with expected title and description |
no | 5-major | |
All usages of AlloyEditor are properly replaced, meaning there's no functionality loss | Given a portal site with Speedwell site template When navigate to Global Menu > Commerce > Products And When Edit an virtual product Then Can type text in the Full Description section in Details tab/Terms of Use section in Virtual tab. Icons in the toolbar (Style, Image, Table etc.) work properly. And Then Able to save the product And Then View saved product with expected content |
no | 5-critical | |
Given a portal site with Speedwell site template When navigate to Global Menu > Commerce > Channels, select the site type channel And When Edit the Money Order Payment Method, check Active Then Can type text in the Message section in Configuration page. Icons in the toolbar (Style, Image, Table etc.) work properly. And Then Able to save the method And Then View saved method with expected content |
no | 4-major |
Exploratory testing to consider:
Test Scenarios | Covered by frontend/backend Unit Test? | Test Priority (business impact) | Firefox Pass/Fail |
Edge Pass/Fail |
---|---|---|---|---|
Manual testing basic scenarios above on FF and Edge browsers | no | 3-medium |
Attachments
Issue Links
- Testing discovered
-
LPS-125953 Spike - Plan how to refactor alloyeditor mentions in poshi test files
-
- Open
-
- links to