-
Notifications
You must be signed in to change notification settings - Fork 669
Testing Scenarios 2.2
Klaas Freitag edited this page Apr 11, 2016
·
10 revisions
If you sync a lot of small files, it should be faster than with 2.1.2.
If you sync with a server 6, you should get a red warning and the sync folder should get paused.
When upgrading from a working 2.1.x installation on Windows to 2.2, the client should not ask for a password.
Test Handle errors of database transactions #4632
This error was reproduceable only if the client could open the sync journal on start, but later looses the file. That we could do on windows performing these steps:
- Sync to a removeable file system, such as USB disk or USB stick, formatted NTFS
- During sync, hibernate the computer
- Remove the disk
- Wake the machine again. AFTER it started, plug the disk in again. That will make the client start without disk.
What should happen is that the client shows an error for a short time and than starts to sync again. What must not happen is that the client can not query the database anymore, log a lot of errors (check using the client log file) and/or forget the selective sync settings.
☁️