Assimilate Senna.js inside DXP codebase

• Type: Epic
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: None
• Component/s: SPA Engine (Senna)
• Labels:
  • 7.4-ce-ga1
  • fc_20_11
  • fi-s-dxp
  • team_fi_epic_category_platform_architecture
• Epic/Theme:
  • FI_Platform_Evolution
• Epic Status: To Do

Epic Information

Senna.js has been a key piece of our infrastructure since it was introduced back in DXP 7.0 to create Automatic Single Page Applications

Being open source at heart, we created Senna as an external library with good popularity and visibility at the time.

The frontend ecosystem has evolved a lot since Senna.js was created and there are nowadays many different approaches for building SPAs that make Senna.js less relevant than in the past.

The goal of this epic is to assimilate Senna.js codebase inside DXP to simplify the maintenance and properly signal the current state of the library to external developers.

Acceptance Criteria

• Senna.js codebase is integrated in DXP and no longer required through an external npm dependency
• Assimilated codebase is updated to remove unnecessary dependencies like metal-*

Test Information

Test Scenarios

Requirement	Test Scenarios	Test Priority (business impact)	Covered by frontend/backend Unit Test?	Chrome Pass/Fail	Edge Pass/Fail
LPS-122509	Given Portal started with SPA enabled (This is by default). When Access to http://localhost:8080 and go to browser develper tool (F12). Then Assert body section has id attribute that contains senna-surface.	5 - critical	yes
	Given Portal started with SPA enabled (This is by default). When Navigate to Web Content admin. Then Assert that spa loading bar appears on top when page is loading.	5 - critical	yes
	Given Portal started with SPA enabled (This is by default). Navigate to Web Content. When Go to Blogs, and go back to Web Content. Then Assert that spa loading bar only appears when go to Web Content at the first time.	5 - critical	yes
	Given A Blog entry with long content displays in page. When Scroll the page down to the bottom of the blog and go to Web Content. Then Clicking back button of browser will redirect to the bottom of the blog.	5 - critical	yes

Exploratory testing to consider:

Test Scenarios	Test Priority (business impact)	Covered by frontend/backend Unit Test?
Given Portal started with SPA enabled. When Access to portal with FF, Edge, Chrome, Safari. Then SPA should work as expected.	2 - low	no
Given Portal started with SPA enabled. When Access to portal on mobile device (smart phone, tablet). Then SPA should work as expected.	2 - low	no

Performance testing to consider:
Will create another ticket to identify how to test and use what tool.