[MGNLUI-2794] Create tests for ContentAppMigrationTask and its sub-tasks Created: 10/Apr/14  Updated: 27/May/14  Resolved: 02/May/14

Status: Closed
Project: Magnolia UI
Component/s: configuration, testing
Affects Version/s: None
Fix Version/s: 5.3

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-2781 As a module developer, I can upgrade ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: JCR-agnostic content apps migration
Sprint: 5.3 Sprint 6

 Description   

Create tests for ContentAppMigrationTask; ideally they should be available / usable from those modules which added the ContentAppMigrationTask to their MVH.



 Comments   
Comment by Christoph Meier [ 10/Apr/14 ]

Remove the not very generic methods in ContentAppModuleVersionHandlerTest which are testing these migration-tasks, too.
But add a concrete implementation of AbstractContentAppMigrationTaskTest in the test-package info.magnolia.ui.contentapp.setup.for5_3 which tests some of the content-apps of admin-central.

Comment by Christoph Meier [ 10/Apr/14 ]

commit onto master: https://git.magnolia-cms.com/gitweb/?p=magnolia_ui.git;a=commit;h=fb4a2a8e07702699a5c8391abb36dd7f02b81bb9

Comment by Mikaël Geljić [ 30/Apr/14 ]

Test for ContentAppMigrationTask shouldn't be abstract, shouldn't be a version-handler test case either.
Then, MVH tests for 5.3 migrated modules should have one test to check module specific upgrade (i.e. not test the ContentAppMigrationTask again).

Reassigning to me.

Generated at Mon Feb 12 09:00:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.