Automate the maintenance release QA process where possible (MAGNOLIA-5564)

[MAGNOLIA-5202] Crawling for pages in edit and preview mode doesn't work Created: 25/Jul/13  Updated: 15/Mar/21  Resolved: 15/Mar/21

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:
1.) directly test the page

  • should be done ASAP

2.) test in the app

  • probably very slow
  • more time consuming to create
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

Generated at Mon Feb 12 04:02:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.