Skip to content

Testing Scenarios 2.2

Jump to bottom
Klaas Freitag edited this page Apr 15, 2016 · 10 revisions

More parallelism for file transfers

If you sync a lot of small files, it should be faster than with 2.1.2.

Syncing with outdated server

If you sync with a server 6, you should get a red warning and the sync folder should get paused.

Test with new Credential store on Windows

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:

  1. Sync to a removeable file system, such as USB disk or USB stick, formatted NTFS
  2. During sync, hibernate the computer
  3. Remove the disk
  4. 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.

Notifications #3733

To test notifications there are two ways:

  1. Create a remote share. The user who is shared with will receive a notification. It has Accept- and Decline buttons. After the user selected one of the two buttons, the notification will go away
  2. The announcement app. With it, the admin can create simple announcements for all users. On the client the user can close this using a Close-Button. Since it is under the Admins control to remove the announcement, it re-appears on new start of the client. That is intended as the notifications are not stored locally.

The user receives tray notifications if new notifications show up.

The client polls for new notifications every 5 minutes by default, which can be changed through the config file with parameter notificationRefreshInterval.

Overlay Icons

The overlay icon SocketAPI which communicates to the native file manager plugins from client side got some significant changes. It is important to do good general testing of the overlay icon functionality.

Specifically:

  • Do the overlay icons reflect the overall status such as Synced, Status "to sync", Error, Ignored?
  • Behavior if the sync of a folder is paused
  • Disconnect and reconnect behavior if the client is closed and re-started. Do the icons come back properly.
  • Across all platforms Windows, Mac and Linux as there is a lot of platform specific code involved.

☁️

Clone this wiki locally