[MGNLCE-263] Integration test of SPA being used in the page editor Created: 09/Jun/20 Updated: 17/Mar/21 Resolved: 08/Mar/21 |
|
| Status: | Closed |
| Project: | Community Edition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.7 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Robert Šiška |
| Resolution: | Done | Votes: | 0 |
| Labels: | VN-Implementation, VN-Testing | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d 3.5h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Epic Link: | SPA Editor |
| Sprint: | HL & LD 22, HL & LD 23 |
| Story Points: | 3 |
| Description |
|
To ensure that things do not break, create a few integration tests which test the SPA editing libraries running in the context of the Magnolia Page Editor. They could test the demo projects included in the frontend libraries repository. For example:
Probably these tests will be similar to the existing Pages app selenium tests.
Some planned tests: https://jira.magnolia-cms.com/issues/?jql=labels%20%3D%20functional-tests |