diff --git a/tests/acceptance/features/apiBasic/addUser.feature b/tests/acceptance/features/apiBasic/addUser.feature deleted file mode 100644 index c98b81c4be..0000000000 --- a/tests/acceptance/features/apiBasic/addUser.feature +++ /dev/null @@ -1,18 +0,0 @@ -@api @provisioning_api-app-required @skipOnLDAP -Feature: add user - As an admin - I want to be able to add users - So that I can give people controlled individual access to resources on the ownCloud server - - Scenario Outline: admin creates a user - Given using OCS API version "" - And user "brand-new-user" has been deleted - When the administrator sends a user creation request for user "brand-new-user" password "%alt1%" using the provisioning API - Then the OCS status code should be "" - And the HTTP status code should be "200" - And user "brand-new-user" should exist - And user "brand-new-user" should be able to access a skeleton file - Examples: - | ocs_api_version | ocs_status_code | - | 1 | 100 | - | 2 | 200 | diff --git a/tests/acceptance/features/apiBasic/uploadFile.feature b/tests/acceptance/features/apiBasic/uploadFile.feature deleted file mode 100644 index bea7e0ae59..0000000000 --- a/tests/acceptance/features/apiBasic/uploadFile.feature +++ /dev/null @@ -1,18 +0,0 @@ -@api -Feature: upload file - As a user - I want to be able to upload files - So that I can store and share files between multiple client systems - - Scenario Outline: upload a file and check download content - Given using OCS API version "" - And user "Alice" has been created with default attributes and without skeleton files - And using DAV path - When user "Alice" uploads file with content "uploaded content" to "/upload.txt" using the WebDAV API - Then the content of file "/upload.txt" for user "Alice" should be "uploaded content" - Examples: - | ocs_api_version | dav_version | - | 1 | old | - | 1 | new | - | 2 | old | - | 2 | new | diff --git a/tests/acceptance/features/apiBasic/webDavPUTAuthInvalid.feature b/tests/acceptance/features/apiBasic/webDavPUTAuthInvalid.feature deleted file mode 100644 index 79f0b3adb5..0000000000 --- a/tests/acceptance/features/apiBasic/webDavPUTAuthInvalid.feature +++ /dev/null @@ -1,26 +0,0 @@ -@api -Feature: attempt to PUT files with invalid password - - Background: - Given user "Alice" has been created with default attributes and without skeleton files - And user "Alice" has created folder "/PARENT" - - Scenario: send PUT requests to webDav endpoints as normal user with wrong password - When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "invalid" about user "Alice" - | endpoint | - | /remote.php/webdav/textfile0.txt | - | /remote.php/dav/files/%username%/textfile0.txt | - | /remote.php/webdav/PARENT | - | /remote.php/dav/files/%username%/PARENT | - | /remote.php/dav/files/%username%/PARENT/parent.txt | - Then the HTTP status code of responses on all endpoints should be "401" - - Scenario: send PUT requests to webDav endpoints as normal user with no password - When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "" about user "Alice" - | endpoint | - | /remote.php/webdav/textfile0.txt | - | /remote.php/dav/files/%username%/textfile0.txt | - | /remote.php/webdav/PARENT | - | /remote.php/dav/files/%username%/PARENT | - | /remote.php/dav/files/%username%/PARENT/parent.txt | - Then the HTTP status code of responses on all endpoints should be "401" diff --git a/tests/acceptance/features/apiOcisSpecific/apiFavorites-favorites.feature b/tests/acceptance/features/apiOcisSpecific/apiFavorites-favorites.feature deleted file mode 100644 index 95f9a387a2..0000000000 --- a/tests/acceptance/features/apiOcisSpecific/apiFavorites-favorites.feature +++ /dev/null @@ -1,25 +0,0 @@ -@api -Feature: favorite - - Background: - Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files - And user "Alice" has uploaded file with content "some data" to "/textfile0.txt" - And user "Alice" has uploaded file with content "some data" to "/textfile1.txt" - And user "Alice" has uploaded file with content "some data" to "/textfile2.txt" - And user "Alice" has uploaded file with content "some data" to "/textfile3.txt" - And user "Alice" has uploaded file with content "some data" to "/textfile4.txt" - And user "Alice" has created folder "/FOLDER" - And user "Alice" has created folder "/PARENT" - And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt" - - @skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-276 - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Favorite a folder - Given using DAV path - When user "Alice" favorites element "/FOLDER" using the WebDAV API - Then the HTTP status code should be "500" - Examples: - | dav_version | - | old | - | new | diff --git a/tests/acceptance/features/apiOcisSpecific/apiVersions-fileVersions.feature b/tests/acceptance/features/apiOcisSpecific/apiVersions-fileVersions.feature index 02dbd7db18..f03ba7eb15 100644 --- a/tests/acceptance/features/apiOcisSpecific/apiVersions-fileVersions.feature +++ b/tests/acceptance/features/apiOcisSpecific/apiVersions-fileVersions.feature @@ -16,16 +16,6 @@ Feature: dav-versions Then the version folder of file "/davtest.txt-olddav-oldchunking" for user "Alice" should contain "0" elements And as "Alice" file "/davtest.txt-newdav-newchunking" should not exist - @skipOnOcis-OCIS-Storage @issue-ocis-reva-17 @issue-ocis-reva-56 - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario: Upload a file twice and versions are available using various chunking methods - When user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms using the WebDAV API - And user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms using the WebDAV API - Then the version folder of file "/davtest.txt-olddav-regular" for user "Alice" should contain "1" element - And the version folder of file "/davtest.txt-newdav-regular" for user "Alice" should contain "1" element - Then the version folder of file "/davtest.txt-olddav-oldchunking" for user "Alice" should contain "1" element - And as "Alice" file "/davtest.txt-newdav-newchunking" should not exist - @skipOnOcis-OC-Storage @issue-ocis-reva-17 @issue-ocis-reva-56 # after fixing all issues delete this Scenario and use the one from oC10 core Scenario: Upload a file twice and versions are available using various chunking methods diff --git a/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature b/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature index caada530f0..38118528be 100644 --- a/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature +++ b/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature @@ -31,14 +31,4 @@ Feature: move (rename) file Examples: | dav_version | | old | - | new | - - @skipOnOcis-OC-Storage @issue-ocis-reva-211 @skipOnOcis-OCIS-Storage - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: renaming to a file with special characters - When user "Alice" moves file "/textfile0.txt" to "/" using the WebDAV API - Then the HTTP status code should be "201" - And the content of file "/" for user "Alice" should be "" - Examples: - | renamed_file | - | #oc ab?cd=ef# | + | new | \ No newline at end of file diff --git a/tests/acceptance/features/apiOcisSpecific/apiWebdavOperations-downloadFile.feature b/tests/acceptance/features/apiOcisSpecific/apiWebdavOperations-downloadFile.feature deleted file mode 100644 index 7dc49b2f84..0000000000 --- a/tests/acceptance/features/apiOcisSpecific/apiWebdavOperations-downloadFile.feature +++ /dev/null @@ -1,24 +0,0 @@ -@api -Feature: download file - As a user - I want to be able to download files - So that I can work wih local copies of files on my client system - - Background: - Given user "Alice" has been created with default attributes and without skeleton files - And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" - And user "Alice" has uploaded file with content "Welcome this is just an example file for developers." to "/welcome.txt" - - @skipOnOcis-OC-Storage @issue-ocis-reva-98 - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Get the content-length response header of a pdf file - Given using DAV path - And user "Alice" has uploaded file "filesForUpload/simple.pdf" to "/simple.pdf" - When user "Alice" downloads file "/simple.pdf" using the WebDAV API - And the following headers should not be set - | header | - | OC-JobStatus-Location | - Examples: - | dav_version | - | old | - | new | diff --git a/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature b/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature deleted file mode 100644 index f98c1a400b..0000000000 --- a/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature +++ /dev/null @@ -1,21 +0,0 @@ -@api @issue-ocis-reva-57 -Feature: set file properties - As a user - I want to be able to set meta-information about files - So that I can reccord file meta-information (detailed requirement TBD) - - Background: - Given using OCS API version "1" - And user "Alice" has been created with default attributes and without skeleton files - - @skipOnOcis-OC-Storage @issue-ocis-reva-276 @skipOnOcis-OCIS-Storage - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: Setting custom DAV property - Given using DAV path - And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt" - When user "Alice" sets property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testcustomprop.txt" to "veryCustomPropValue" using the WebDAV API - Then the HTTP status code should be "500" - Examples: - | dav_version | - | old | - | new | diff --git a/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature b/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature index 67d0594c54..a72a3ceb6b 100644 --- a/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature +++ b/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature @@ -38,17 +38,6 @@ Feature: get file properties | old | /file ?2.txt | webdav\/file%20%3F2\.txt | | new | /file ?2.txt | dav\/files\/%username%\/file%20%3F2\.txt | - @skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: upload a file to content - Given using DAV path - When user "Alice" uploads file with content "uploaded content" to "" using the WebDAV API - Then the HTTP status code should be "500" - Examples: - | dav_version | file_name | - | old | /file ?2.txt | - | new | /file ?2.txt | - @issue-ocis-reva-214 @skipOnOcis-OCIS-Storage # after fixing all issues delete this Scenario and use the one from oC10 core Scenario Outline: Do a PROPFIND of various folder names diff --git a/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature b/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature index b4b78ebc5d..b722d7b353 100644 --- a/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature +++ b/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature @@ -8,17 +8,6 @@ Feature: upload file Given using OCS API version "1" And user "Alice" has been created with default attributes and without skeleton files - @skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage - # after fixing all issues delete this Scenario and use the one from oC10 core - Scenario Outline: upload a file and check download content - Given using DAV path - When user "Alice" uploads file with content "uploaded content" to using the WebDAV API - Then the content of file for user "Alice" should be "" - Examples: - | dav_version | file_name | - | old | "file ?2.txt" | - | new | "file ?2.txt" | - @skipOnOcis-OC-Storage @issue-product-127 @skipOnOcis-OCIS-Storage # this scenario passes/fails intermittently on OC storage, so do not run it in CI # after fixing all issues delete this Scenario and use the one from oC10 core