-
Type:
Technical Testing
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Fragment Administration
-
Labels:None
-
Test Type:
Case 1:
Can apply itemSelector to fragment configuration
- Create a new fragment with configuration
{ "fieldSets":[{ "fields":[{ "name":"itemSelector", "description":"", "label":"Content", "type":"itemSelector", "typeOptions":{ "enableSelectTemplate":true }, }] }] }
- Assert there are no configuration errors in the fragment editor and you can publish fragment
Case 2:
If a fragment contains the itemSelector configuration there is a configuration field to select an existing content of type blog entry, web content, or document
- Add a fragment with itemSelector configuration
- Create a content page
- Add fragment to page and select fragment configuration
- Assert there is a field that allows the selection of content type: blog entry, web content, and document
Case 3:
Assert correct content is selected when using itemSelector
- Add 3 different web contents
- Add a fragment with itemSelector configuration(also add code in HTML section to display selected content, ex:${configuration.itemSelector})
- Create a content page
- Add fragment to page and select fragment configuration
- Change the field to select each web content and assert the correct web content is being displayed
Case 4:
Verify the itemSelector fragment configuration can select an asset in all Page Editor locations
- Create a new fragment with itemSelector configuration
- Create a new content page, content page template, and display page template
- Assert you can add fragment to each page and can select an asset using the itemSelector configuration
- Testing discovered
-
LPS-101552 When adding fragment configuration option to select an existing content, display style is present for web content selection
- Closed