Testing Scenarios 2.0

The config (account and folders) from the previous version should be kept when upgrading
One can now configure several accounts by pressing on the new account button in the general settings
accounts can be deleted
the accounts show up in the owncloud tray icon menu and the actions there work correctly
the overall tray icon status correctly adjusts as folders and accounts change state
one can add and remove folders per account and the changes persist correctly when the client restarts
the password dialog contains the account and user name

Shared folder of more than 100M are not sync'ed by default
when there is a new shared folder of more than 100M, one get a notification in the account settings.
The selective sync items of such folder are red and disabled by default until confirmed

on Windows, now long Pathnames that are longer than 260 bytes can be used.
To test, create deep pathes and put files in, let sync. Verify that all operations like adding, editing, removing, renaming of files works in deep directories and all is propagated nicely to the server.

on Windows, the installer now uses a "clean" name for building up the default install path, ie. without colons and such. The update case needs to be tested. Please find a branding that has a different APPLICATION_NAME and APPLICATION_SHORTNAME. Install the old version first, and update to the new 2.0.0. After that, the old directory (for example c:\program files\my owncloud\owncloud.exe) should be gone, but the new one c:\program files\myowncloud\owncloud.exe) should be there, assuming that APPLICATION_SHORTNAME=myowncloud and APPLICATION_NAME="my owncloud".

When upgrading a 2.0 pre ownCloud (applies to snapshots past 15.07.2015) to another one or 2.0 alpha, beta, rc or final, you should not see a page in the upgrade wizard offering to remove the application's AppData (see screenshot on original bug for reference).
When uninstalling 2.0, you should not see a page in the upgrade wizard offering to remove the application's AppData (see screenshot on original bug for reference). *When upgrading from 1.8.x or earlier, to a 2.0 snapshot (applies to snapshots past 15.07.2015), alpha, beta, rc or final, you should see a page in the upgrade wizard offering to remove the application's AppData (see screenshot on original bug for reference). Reason: This dialog is provided by the already installed version.

When 'Use system proxy' is selected, a proxy may still need authentication.
In such a case the client will pop up a dialog asking for username and password.
This password is saved and does not need to be reentered when the client restarts.
It even persists when the system proxy changes to another server and back.

Test hints:

mitmproxy -p 8080 --singleuser foo:bar
http_proxy=http://localhost:8080 ./owncloud

Two implementations of the finder plugin are available, activated depending on OS X's version, one on 10.9 and earlier and one on 10.10
Both plugins have changed the way that they connect to the client to fetch file sync statuses, they now use a synchronous NSConnection instead of a unix socket. This means that heavy synchronisations on old machines could be problematic and would be worth testing.
We have to change the way that we finish a sync in the >10.10 version, in which case some files could be stuck in a syncing state even after the sync is done.
The plugin should try to reconnect automatically to the client every 5 seconds in any situation

☁️

Provide feedback