[MGNLCE-333] Test to ensure that SSR is supported Created: 09/Dec/20 Updated: 08/Sep/22 Resolved: 06/Sep/22 |
|
| Status: | Closed |
| Project: | Community Edition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0, 6.2.24 |
| Type: | Task | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Robert Šiška |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||
| Template: |
|
|||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||
| Task DoR: |
Empty
|
|||||||||||||||||||||||||
| Date of First Response: | ||||||||||||||||||||||||||
| Epic Link: | SaaS TPR - SPA Tests | |||||||||||||||||||||||||
| Sprint: | DevX 17, DevX 18 | |||||||||||||||||||||||||
| Story Points: | 8 | |||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||
| Description |
|
Description: Add a test to ensure that we don't introduce any code that would prevent a server side rendering. It is easy to forget this so a test would ensure that we don't break this important capability. We want to ensure that this works: https://jira.magnolia-cms.com/browse/MGNLFE-23
Discovered: This will be an automated integration test. We need three simple test projects that do serverside rendering. |
| Comments |
| Comment by Canh Nguyen [ 23/May/22 ] |
|
I think we could go with integration tests or do manual test before releasing a new version. We need to create new three SSR projects for three frameworks:
If we go with integration tests, we could create new projects base on projects that we're using for integration tests. If we go with manual tests, then we can create new projects in samples folder in frontend-helpers. |
| Comment by Christopher Zimmermann [ 23/May/22 ] |
|
I'm very much in favor of these being automated tests. Then they cannot be forgotten as easily. and they don't slow us down when releasing new versions of the library.. |
| Comment by Christopher Zimmermann [ 23/May/22 ] |
|
And we can hook them into the SaaS automated testing to ensure changes on SaaS dont break our SSR apps either |
| Comment by Robert Šiška [ 31/Aug/22 ] |
|
Reopened: Revert until the 6.2.23 is released. We need to revert from both release/6.2 and master because both branches use the same pipeline. |