Automate the maintenance release QA process where possible
(MAGNOLIA-5564)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | integration tests |
| Affects Version/s: | 5.0 |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Critical |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | maintenance, next | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
URLs of the pages in edit mode and in preview mode are different in 5.0 than those used in 4.5, therefore scripts for crawling are not checking pages for rendering errors in edit and preview mode anymore, increasing the possibility of releasing Magnolia 5.x with broken rendering. |
| Comments |
| Comment by Daniel Lipp [ 13/Nov/13 ] |
|
we should probably do in two steps:
2.) test in the app
|
| Comment by Roman Kovařík [ 11/Dec/13 ] |
|
Moving out of 5.2.1 to 5.2.x. We have to go trough pages via page editor on author instance manually when doing QA of 5.2.1 |