maryjane
/
syncevolution
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
syncevolution/test/testcases/synctests/googlecontacts/eds_contact/testUpdateRemoteWins/README

6 lines
285 B
Plaintext
Raw Normal View History

testing: simulate remote item manipulation Traditionally, SyncEvolution only modified remote data via syncing. This is not enough because it does not cover data on the remote side that SyncEvolution cannot sync. The new tests solve this by using the command line's import/update operations which modify data more or less directly. Now we can test: - downloading data created remotely - uploading data via sync, export directly, compare - simulate conflicts with changes made remotely The download and upload test include full round-trips, i.e. the initial transfer plus a change that needs to be synced back. Because this is highly dependent on the exact data stored by the peer, all these tests depend on per-peer test data and scripts for modifying that data. The tests only get enabled if the test data is found. The initial test data covers Apple Calendar server, EDS<->EDS and Google Contacts.
2014-04-23 14:53:23 +02:00
Because the remote side wins and replaces values for common
properties, the X-EVOLUTION-UI-SLOT gets lost when receiving a remote
update or having the remote side win an update conflict.
Import Upstream version 1.5.3
2021-09-29 23:01:46 +02:00
local-synced takes that into account. - no PHOTO data because the server may re-encode the image