diff --git a/Desktop/Regression_Test_Plan_Minor_Release.md b/Desktop/Regression_Test_Plan_Minor_Release.md index bc48598c..1b472564 100644 --- a/Desktop/Regression_Test_Plan_Minor_Release.md +++ b/Desktop/Regression_Test_Plan_Minor_Release.md @@ -1,3 +1,6 @@ +1. Create a new testplan ticket in the owncloud/client repo, copy the text below into it: + +``` # Regression test for the Desktop Client [Test Plan Template](https://github.com/owncloud/QA/blob/master/Desktop/Regression_Test_Plan_Minor_Release.md) @@ -5,40 +8,52 @@ ## Previous requirements Have a Desktop Client vX.X.0 ready to be used for testing. - -Prepare a OC server with ssl activated and trusted certificates. - + -> download URL + Prepare a OC server with ssl activated and trusted certificates. + -> server URL Prepare a 10.2.1 server with ssl activated and trusted certificates. - `env OC10_VERSION=10.2 bash make_oc10_apps.sh --` - + -> ... Have a LDAP server ready to be used with owncloud with two external storages of your choice (SFTP and WND) - `env OC10_DNSNAME=oc1080-ldap-DATE bash make_oc10_apps.sh oauth2 user_ldap password_policy files_pdfviewer windows_networ_drive=2.0.0` - + -> ... + Optional: Have an Active Directory server ready to be used with owncloud. ## Testing -1. Add [Regression_Test_Plan_Patch](https://github.com/owncloud/QA/blob/master/Desktop/Regression_Test_Plan_Patch_Release.md) items in a separate comment (all platforms, migration tests). - -2. Add the section below to the initial comment of the release ticket: * [ ] 1. Install/Update - Connect - Login @tester1 - * https://github.com/owncloud/client/issues/xxxx#issuecomment-xxxxxxxxx + -> https://github.com/owncloud/client/issues/xxxx#issuecomment-xxxxxxxxx * [ ] 2. Folders -* [ ] 3. Files -* [ ] 4. Move files and folders -* [ ] 5. Edit Files -* [ ] 6. Delete Files and Folders -* [ ] 7. Sync process -* [ ] 8. Without connection + -> ... +* [ ] 3. Files + -> ... +* [ ] 4. Move files and folders + -> ... +* [ ] 5. Edit Files + -> ... +* [ ] 6. Delete Files and Folders + -> ... +* [ ] 7. Sync process + -> ... +* [ ] 8. Without connection + -> ... * [ ] 9. Sharing + -> ... * [ ] 9.1 Share link * [ ] 9.2 Share with Users and Groups + -> ... * [ ] 10. Selective_Sync * [ ] 10.2 "Skip folders configuration" -* [ ] 10.3 "Add Folder..." -* [ ] 11. Overlay_icons +* [ ] 10.3 "Add Folder..." + -> ... +* [ ] 11. Overlay_icons + -> ... +``` + +2. Add the [Regression_Test_Plan_Patch](https://github.com/owncloud/QA/blob/master/Desktop/Regression_Test_Plan_Patch_Release.md) items in a separate comment (test all platforms + migration). -3. Copy each set (1. - 11.) of the minor release tests to a separate comment in the relase ticket and add the links above. If more persons are testing, you can write the name beside the headline. +3. Copy each set (1. - 11.) of the minor release tests into a separate comment and add the links above. If more persons are testing, write the name beside the headline. 4. For each test set, choose a random platform win/linux/mac, unless test items specify otherwise. Record which platform was used. @@ -63,8 +78,8 @@ TestID | Test Case | Steps to reproduce |Expected Result |Result | Related Comme 6 :robot:| Verify that all contents of the server account is synced to the local folder | 1. Choose to sync everything from server (default option) 2. Select the local folder desired | All the files/folders are synced down | :heavy_check_mark: | tst_addAccount | 7 | Verify that only the folder(s) selected are synced in the local folder | 0. Disable VFS, 1. Click on Choose what to sync 2. The remote folder(s) are shown, select which you want to sync 3. Select the local folder |The selected folders selected are synced | :construction: | | 8 | Verify that you can skip folder configuration | 1. Click on "Manually create folder sync connection" | No settings dialog opens, the account shows only an "Add Folder Sync Connection" button. | :construction: | | -9 | Connect to a server with LDAP (or optinally AD) | 0. Only for minor releases, 1. Setup owncloud server with openldap, 2. Connect. | Make sure no technical user name shows up in UI (e.g. account name, sharing...) | | | -10 | Connect to a 8.1.x server | 0. Only for minor releases, 1. `docker run -ti -p 8181:80 owncloud:8.1`, 2. Connect. A warning appears: "The server version 8.1.12.2 is unsupported", but syncing works. | :construction: | | +9 | Connect to a server with LDAP (or optinally AD) | 0. Only for minor releases, 1. Setup owncloud server with openldap, 2. Connect. | Make sure no technical user name shows up in UI (e.g. account name, sharing...) | :construction: | | +10 | Connect to a 8.1.x server | 0. Only for minor releases, 1. `docker run -ti -p 8181:80 owncloud:8.1`, 2. Connect. A warning appears: "The server version 8.1.12.2 is unsupported", but syncing works. | | :construction: | | ### 2. Folders @@ -78,17 +93,17 @@ TestID | Test Case | Steps to reproduce| Expected Result | Result | Related Comm 2 | Verify that you can create one folder with long name | 1. Go to local sync folder 2. Create a single folder with a long name (59 characters+a terminating zero bytes) 3. Wait for sync |The folder visible on the server | | | 3 | Verify that you can create one folder with special characters in the name | 1. Go to local sync folder 2. Create a single folder with a special character(s) in the name (e.g $%ñ&) 3. Wait for sync | The folder appears on the server | | | 4 | Verify that you can sync many subfolders | 1. Go to local sync folder 2. Copy a folder with 5 empty subfolders and 5 folders containing files 3. Wait for sync | All 10 subfolders are visible on the server | | | -8 | Verify that you can create multiples folders at once | 1. Create a folder with 400 subfolders outside the sync root, 2. Move that into the sync root, 3. Wait for sync | All 400 folders appear on the server | | | -5 | Verify that you can copy one folder | 1. Go to local sync folder 2. Create a single folder with some files in it 3. Copy and paste the folder 4. Wait for sync | Both copies appears on the server | | | -6 | Verify that you can create a subfolder with long name | 1. Go to local sync folder, 2. Create a folder called "Folder1" 3. Create a subfolder called "LUsgzq!0k02sek+szBqrzN5=R#UJpWql&rwhnYVb~Gh!l!” (optionally up to 255 characters), 4. This subfolder had a file called ilppng.PNG inside it 5. Wait for sync |The files are synced correctly| | | -7 | Verify pre existing folders in local (Desktop client) are copied over to the server | 1. Turn off the Desktop client 2. Go to local sync folder 3. Create several folders inside the Desktop Client folder at several different levels, 4. Turn ON the Desktop Client | Folders appear on the server | | | -8 | Filenames that are rejected by the server are reported | 1. Go to local sync folder, 2. Create a file called `"a\\a"` (or another name not accepted by the server), 3. Wait for sync | The sync status reports an error, the file s not synced| | | -9 | Verify one empty folder with a length longer than the allowed limit will not be synced | 1. Go to local sync folder 2. Create a single empty folder with a name longer than that allowed by ILP (more than 59 characters) 3. Look at the Via Web repository 4. Repeat this with a folder at the root level, and in various subfolders up to 5 levels deep 5. Sync |At the Via Web the folder has not been synced| | | -10| Sync works for .zip/.rar files with elaborate internal folder structures | 1. Create a .zip file with many internal folders and files 2. Copy the .zip file to the Desktop Client folder 3. Unzip the .zip file inside the Destop Client folder |1. Make sure you get a popup saying that all the extracted files have synced. 2. Look at Via Web and make sure that the folder has been synced over| | | -11| Files that error with API should try 3 times, and then blacklist | 1. Try to sync a folder that has more than 65 characters 2. Then sync it with some contents, it should try three times and then be blacklisted 3. If you rename the folder it should try again, and succeed if the name is less than 65 characters |The folder is synced| | | -12| Invalid system names | 1. On the server, create folders named 'COM' and 'test%' and two files named 'PRN' and 'foo%' | A MacOS client syncs down 'COM' and 'PRN' but not 'test% or 'foo%' | | | -13| Invalid system names | 1. On the server, create folders named 'COM' and 'test%' and two files named 'PRN' and 'foo%' | A windows client syncs down 'test%' and 'foo%' but not 'COM' or 'PRN' | | Folder named COM will be synced. | -14| Invalid system names | 1. On the server, create folders named 'COM' and 'test%' and two files named 'PRN' and 'foo%' | A Linux client syncs down all. | | All folder will be synced | +5 | Verify that you can create multiples folders at once | 1. Create a folder with 400 subfolders outside the sync root, 2. Move that into the sync root, 3. Wait for sync | All 400 folders appear on the server | | | +6 | Verify that you can copy one folder | 1. Go to local sync folder 2. Create a single folder with some files in it 3. Copy and paste the folder 4. Wait for sync | Both copies appears on the server | | | +7 | Verify that you can create a subfolder with long name | 1. Go to local sync folder, 2. Create a folder called "Folder1" 3. Create a subfolder called "LUsgzq!0k02sek+szBqrzN5=R#UJpWql&rwhnYVb~Gh!l!” (optionally up to 255 characters), 4. This subfolder had a file called ilppng.PNG inside it 5. Wait for sync |The files are synced correctly| | | +8 | Verify pre existing folders in local (Desktop client) are copied over to the server | 1. Turn off the Desktop client 2. Go to local sync folder 3. Create several folders inside the Desktop Client folder at several different levels, 4. Turn ON the Desktop Client | Folders appear on the server | | | +9 | Filenames that are rejected by the server are reported | 1. Go to local sync folder, 2. Create a file called `"a\\a"` (or another name not accepted by the server), 3. Wait for sync | The sync status reports an error, the file s not synced| | | +10 | Verify one empty folder with a length longer than the allowed limit will not be synced | 1. Go to local sync folder 2. Create a single empty folder with a name longer than that allowed by ILP (more than 59 characters) 3. Look at the Via Web repository 4. Repeat this with a folder at the root level, and in various subfolders up to 5 levels deep 5. Sync |At the Via Web the folder has not been synced| | | +11| Sync works for .zip/.rar files with elaborate internal folder structures | 1. Create a .zip file with many internal folders and files 2. Copy the .zip file to the Desktop Client folder 3. Unzip the .zip file inside the Destop Client folder |1. Make sure you get a popup saying that all the extracted files have synced. 2. Look at Via Web and make sure that the folder has been synced over| | | +12| Files that error with API should try 3 times, and then blacklist | 1. Try to sync a folder that has more than 65 characters 2. Then sync it with some contents, it should try three times and then be blacklisted 3. If you rename the folder it should try again, and succeed if the name is less than 65 characters |The folder is synced| | | +13| Invalid system names | 1. On the server, create folders named 'COM' and 'test%' and two files named 'PRN' and 'foo%' | A MacOS client syncs down 'COM' and 'PRN' but not 'test% or 'foo%' | | | +14| Invalid system names | 1. On the server, create folders named 'COM' and 'test%' and two files named 'PRN' and 'foo%' | A windows client syncs down 'test%' and 'foo%' but not 'COM' or 'PRN' | | Folder named COM will be synced. | +15| Invalid system names | 1. On the server, create folders named 'COM' and 'test%' and two files named 'PRN' and 'foo%' | A Linux client syncs down all. | | All folder will be synced | ### 3. Files