Verify and fix integration with versioning, test rollback and diff (QAARQ-1)

[QAARQ-5] Test and report if versioning still works with Rabbitmq activation Created: 18/Nov/15  Updated: 17/Dec/18  Resolved: 25/Nov/15

Status: Closed
Project: Queued Asynchronous Activation over RabbitMQ
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Neutral
Reporter: Karel de Witte Assignee: Karel de Witte
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0.5h
Time Spent: 1.5h
Original Estimate: 0.25d

Template:
Date of First Response:

 Comments   
Comment by Thanh Pham [ 19/Nov/15 ]

I created a test case for versioning and it worked correctly:
Environment: 1 Author, 1 Public with Magnolia version 5.4.3, 1 RabbitMQ server
Case 1:

  • Author: Publish a page of Author, the system creates a version of that page
  • Public: apply new data
  • Author: edit some properties of that page, and publish again
  • Public: apply new data
  • Author: choose that page and click "show versions" action --> The dialog displays 2 versions that have different and correct datas
  • Continue with other pages ( edit/publish/show versions... )
    Apply test case 1 for asset, resources app and get the same result.
Comment by Thanh Pham [ 25/Nov/15 ]

Done. The functions work as expected.

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