Testing Scenarios 2.3

Obviously, older feature should be tested too: Desktop client Testing Scenarios

Application Password

Check that for server >= 9.1, the login dialog and the wizard (everywhere a password is needed) show a link to get an app password. And this link should work and point to the location to create the app password. No matter if we were logged in or not in the browser already.

Share Dialog mailto: option

Issue #3261

Check the mail link button on the share dialog

Backup restore options

Issue #5109 & Issue #5260

When the data-finger print is changed, all the files that were changed are backup'ed in a conflict file

External Storage Exclusion

Pull request #5340

See Pull Request for the whole list of AC and development.

Sync same local folder with multiple servers

Issue #3764

Multiple (not the same) accounts can sync the same local sync folder.

Note: there's still some instability with the overlay icons behavior (#3764 (comment)) and the sharing capabilities (#5462, #5463)

Conflict files: use timestamp in filenames

Issue #5273

Multiple editions to a read-only file (conflicts) are translated into multiple conflict files.

Do not blacklist 507 InsufficientStorage

Issue #5346

• After freeing space on the server, files are synced
• The same happens after increasing the user quota

New actions

Sync now

Issue #2158

Forces a sync check in a local sync folder; as: Pause + Resume sync does.

New account...

Issue #5307

When the connection wizard is closed with no accounts set, there's a time triggering event that launches only one wizard again. The button allows to anticipate the event and launch the wizard on demand.

New WebDAV endpoint

Issue #4007

Check if the whole operative is correct and the endpoints

Interesting scenario: add account on an older (<9.0) server and upgrade to a newer version that switches the WebDAV endpoint.

Sync scheduling

Issue #5317: Does not re-include unavailable local sync folders when they are available again.

Now local sync folders that are temporarily unavailable (e.g. mounted drives) should be synced again after they're back (mounted back or placed the folder in the original location). Doesn't matter for how long they were unavailable.

Issue #5290: [2.2.4] Pause synchronization doesn't pause the synchronization

• When using the Pause Synchronization action on the tray menu, the sync is paused (i.e. no time ETA on the tray menu and no network communications)
• In the multi-account scenario, Pause all synchronization pauses all the syncs, not only the current and starts the next queued.

Issue #5477: Logged out accounts stay "Waiting" if unpaused

When logged out and unpausing a folder sync connection, the general tab doesn't show the scheduled, paused message "Waiting..."

Do not trigger syncs if files under hidden directories are modified

Issue #5163

If hidden directories are ignored in general settings, do not initiate the sync after changes are made under their file tree.

Shibboleth bugfixes

Issue #5408 Shibboleth accounts don't work after restart

This was due to DummyCredentials being used for the account if the Skip folder configuration was clicked on the wizard after account creation on restart. Plus old (bogus) accounts are migrated to non-connected.

Issue #5407 The username in SAML logins doesn't appear next to the URL in the account tab

Also, the user name was not displayed next to the URL.

Issue #5469 Shibboleth accounts don't need the credentials to log in after wiping its keychain entry

The issue was that all shibboleth accounts used the same keychain/credentialstore entry for their cookies.

Pull Request #5490 Cookies: Use different DB for different accounts

Also, following the previous; the cookies for each account should be in different CookiesX.db file.

HTTP Redirections

Pull Request #4905

Now every redirection is followed on the client (except loops of >10 jumps and protocol downgrades: https->http) this should fix problems with e.g. multi-tenancy installations.

Remove all cookies when logging out

Pull Request #5383

This issue caused the client to keep cookies containing still valid session tokens sent by modified servers after a log out was made, resulting in unauthenticated logins (i.e. no password & wrong password)

Note: check if this works together with #5490

Overlay improvements:

Issue 5361: Large number of files to sync freezes the application when sending the status to Finder

Issue 4797: Don't rely on hierarchical SyncFileItems to propagate OK statuses to parent folders during sync