Test cases for federation/synchronization features (sync and service modules)

Also check the docs, how the sync job is working. Let's also discuss personally, if there are more detailed questions are surfacing.

Sub Tasks

• Testing the sync module
• Test transferring of data objects in the SyncNode in the service module

changed milestone to %1.0-alpha3 — Playful Platypus

assigned to @chrizz

added P2 label

changed title from Test cases for "SyncJob" to Test cases for federation/synchronization features (sync and service modules)

changed the description

@chrizz While the federation feature is not required for the 1.0 release, this ticket is only scheduled for now, to a.) increase the test coverage and b.) to provide a chance to learn about the implementation of this feature more deeply. In case you are too busy, we can postpone this absolutely.

added P3 label and removed P2 label

added 1 deleted label

added To Do label

mentioned in issue #9 (closed)

added Doing label and removed To Do label

marked the checklist item Testing the sync module as completed

Started this issue to become more familiar with the federation feature and to re-rest some prior fixes related to sync mode.

Tried to implement a test case using the flask unittest framework but encountered limitations concerning multiple instances; so solved using processes running on background threads.

Successfully tested the synchronization of the playlog between two nodes; sync node fetched playlog from main node, but expected the original entry beeing marked as "synced", which is not true. (Should be, right?)

So pausing this issue for now; preventing spending to much effort...

removed Doing label

added To Do label

removed To Do label

added 1 deleted label

added To Do label

added 1 deleted label