[MGNLMIGRATION-259] Improve integration tests for content migration Created: 29/Aug/13  Updated: 15/Mar/21  Resolved: 15/Mar/21

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.x

Type: Improvement Priority: Neutral
Reporter: Jaroslav Simak Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLMIGRATION-258 Add content migration to integration ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Currently, integration tests compare only node types and templates. We should enhance tests to also compare property values and also maybe node names and property names.



 Comments   
Comment by Robert Šiška [ 04/Sep/13 ]

Comparing of property values was disabled on purpose, because a) there were too many trivial differences on demo-project, and b) migration module doesn't affect any property values except templates and node types.
Apart from that, number of properties and their names are still compared.

By the way, since demo-project is being bootstrapped again, there are no integration tests for content migration.
Maybe some sample content could be made for testing purposes.

Generated at Mon Feb 12 10:18:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.