While some fragments can be dynamic, the majority of them are simply static content that once it is on the page it is final. The goal would be that most content pages could be rendered completely static and completely cached to provide the best performance for the end user. Similar to how web content templates have an option for being cacheable or not, fragments should be by default completely cached, and and an option to make them not cacheable if you are adding dynamic functionality.
|Test Scenarios||Test Strategy||Kind of test||Is it covered by FrontEnd ? (JS-Unit)||Is it covered by BackEnd ? (unit or integration)|
|Can check Cacheable for fragments when create them in portal and they are non-Cachable by default||Smoke||Manual||No||No|
|Can check Cacheable for fragments without Read-Only label imported to portal and they are non-Cachable by default||Sanity||Manual||No||No|
|There is no Cacheable option for fragments that are marked with Read-Only label||Regression||Manual||No||No|
|Assert not process loading fragments that are Cacheable when access to content page in edit mode via backend||Sanity||Manual||No||No|