[MAGNOLIA-5564] Automate the maintenance release QA process where possible Created: 19/Dec/13  Updated: 19/Dec/16

Status: Open
Project: Magnolia
Component/s: integration tests
Affects Version/s: 5.2
Fix Version/s: None

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: next
Σ 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:
Relates
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-5202 Crawling for pages in edit and previe... Sub-task Closed  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

Over time magnolia has developed a series of manual tests to help ensure the quality of a release:
http://wiki.magnolia-cms.com/display/DEVINT/Release+QA+Plan

However these are time consuming (at the end of a release when time is precious) and error prone.

Evaluate all manual tests and create automated tests where possible to replace them.


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