React fragments can be generated, compiled and exported to a Liferay Portal. For the time being we are allowing the user to see the fragment type : fragment composition, or "normal" fragment, now we will introduce a type type of fragment called React Fragment.
This type of fragment come with a pre-compiled code and we are not planning to allow the portal to compile it for the moment. As a consequence the user will not be able to edit the Fragment JS code from the portal.
The goal of this story is to allow Fragment developers to distinguish React Fragments from normal fragments so that the developer understand that he/she has restrictions when manipulating react fragments.
Given a Developer has exported a React Fragment from Fragment Toolkit (or Zip deployment)
When the Developer logs in to the portal and visits the fragment list
Then the developer can see listed all the fragments
- and a the React Fragment are shown with a visual marker (as defined in mockup)
|Test Scenarios||Test Strategy||Kind of test||Is it covered by FrontEnd ? (JS-Unit)||Is it covered by BackEnd ? (unit or integration)||Could it be covered by POSHI?|
|Identify the react fragment from fragment list||Critical||Manual||No||No||Yes|