Merge pull request #6165 from owncloud/remove-unneccessary-tag

[tests-only][full-ci]Remove unnecessary tags
2026-05-12 22:39:34 -05:00 · 2023-05-04 13:50:20 +05:45
parent d73ea1318c 65f0b18254
commit 9d4236f5b6
165 changed files with 543 additions and 778 deletions
@@ -962,7 +962,7 @@ def wopiValidatorTests(ctx, storage, accounts_hash_difficulty = 4):

 def coreApiTests(ctx, part_number = 1, number_of_parts = 1, storage = "ocis", accounts_hash_difficulty = 4):
    early_fail = config["apiTests"]["earlyFail"] if "earlyFail" in config["apiTests"] else False
-    filterTags = "~@skipOnGraph&&~@toImplementOnOCIS&&~comments-app-required&&~@federation-app-required&&~@notifications-app-required&&~systemtags-app-required&&~@local_storage&&~@skipOnOcis-%s-Storage&&~@caldav&&~@carddav" % ("OC" if storage == "owncloud" else "OCIS")
+    filterTags = "~@skipOnGraph&&~@skipOnOcis-%s-Storage&&~@carddav" % ("OC" if storage == "owncloud" else "OCIS")
    expectedFailuresFile = "%s/tests/acceptance/expected-failures-API-on-%s-storage.md" % (dirs["base"], storage.upper())

    return {
@@ -12,7 +12,7 @@ then
    if [ "$STORAGE_DRIVER" = "ocis" ]
    then
        export OCIS_REVA_DATA_ROOT=''
-        export BEHAT_FILTER_TAGS='~@toImplementOnOCIS&&~comments-app-required&&~@federation-app-required&&~@notifications-app-required&&~systemtags-app-required&&~@local_storage&&~@skipOnOcis-OCIS-Storage'
+        export BEHAT_FILTER_TAGS='~@skipOnOcis-OCIS-Storage'
        export OCIS_SKELETON_STRATEGY='upload'
        export EXPECTED_FAILURES_FILE='/drone/src/tests/acceptance/expected-failures-API-on-OCIS-storage.md'
    elif [ "$STORAGE_DRIVER" = "s3ng" ]
@@ -710,19 +710,19 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
 - [coreApiTrashbin/trashbinFilesFolders.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L100)
 - [coreApiTrashbin/trashbinFilesFolders.feature:136](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L136)
 - [coreApiTrashbin/trashbinFilesFolders.feature:159](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L159)
- [coreApiTrashbin/trashbinFilesFolders.feature:322](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L322)
- [coreApiTrashbin/trashbinFilesFolders.feature:323](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L323)
- [coreApiTrashbin/trashbinFilesFolders.feature:324](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L324)
- [coreApiTrashbin/trashbinFilesFolders.feature:329](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L329)
- [coreApiTrashbin/trashbinFilesFolders.feature:330](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L330)
- [coreApiTrashbin/trashbinFilesFolders.feature:331](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L331)
- [coreApiTrashbin/trashbinFilesFolders.feature:332](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L332)
- [coreApiTrashbin/trashbinFilesFolders.feature:333](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L333)
+- [coreApiTrashbin/trashbinFilesFolders.feature:305](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L305)
+- [coreApiTrashbin/trashbinFilesFolders.feature:306](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L306)
+- [coreApiTrashbin/trashbinFilesFolders.feature:307](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L307)
+- [coreApiTrashbin/trashbinFilesFolders.feature:312](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L312)
+- [coreApiTrashbin/trashbinFilesFolders.feature:313](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L313)
+- [coreApiTrashbin/trashbinFilesFolders.feature:314](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L314)
+- [coreApiTrashbin/trashbinFilesFolders.feature:315](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L315)
+- [coreApiTrashbin/trashbinFilesFolders.feature:316](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L316)
+- [coreApiTrashbin/trashbinFilesFolders.feature:317](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L317)
 - [coreApiTrashbin/trashbinFilesFolders.feature:334](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L334)
- [coreApiTrashbin/trashbinFilesFolders.feature:351](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L351)
- [coreApiTrashbin/trashbinFilesFolders.feature:371](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L371)
- [coreApiTrashbin/trashbinFilesFolders.feature:425](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L425)
- [coreApiTrashbin/trashbinFilesFolders.feature:462](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L462)
+- [coreApiTrashbin/trashbinFilesFolders.feature:354](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L354)
+- [coreApiTrashbin/trashbinFilesFolders.feature:408](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L408)
+- [coreApiTrashbin/trashbinFilesFolders.feature:445](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature#L445)

 #### [Default capabilities for normal user and admin user not same as in oC-core](https://github.com/owncloud/ocis/issues/1285)
 - [coreApiCapabilities/capabilities.feature:11](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiCapabilities/capabilities.feature#L11)
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @skipOnReva
+@api @skipOnReva
 Feature: sharing
  As a user
  I want to be able to share files when passwords are stored with the full hash difficulty
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: download multiple resources bundled into an archive
  As a user
  I want to be able to download multiple items at once
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: download multiple resources bundled into an archive
  As a user
  I want to be able to download multiple items at once
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Copy test
  As a user
  I want to check the PROPFIND response
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Propfind test
  As a user
  I want to check the PROPFIND response
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Report test
  As a user
  I want to check the share REPORT response
@@ -1,6 +1,6 @@
 # NOTE: for running this feature locally, you need to run oCIS with the following env var:
 # CORS_ALLOWED_ORIGINS=https://aphno.badal
-@api @skipOnOcV10
+@api 
 Feature: CORS headers
  As a user
  I want to send a cross-origin request
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: add users to group
  As a admin
  I want to be able to add users to a group
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: create group
  As an admin
  I want to create a group
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: create user
  As a admin
  I want to create a user
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: delete groups
  As an admin
  I want to be able to delete groups
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: delete user
  As an admin
  I want to be able to delete users
@@ -1,4 +1,4 @@
-@api @skipOnOcV10 
+@api 
 Feature: edit group name
  As an admin
  I want to be able to edit group name
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: edit user
  As an admin
  I want to be able to edit user information
@@ -1,4 +1,4 @@
-@api @skipOnOcV10 @skipOnStable2.0
+@api @skipOnStable2.0
 Feature: get applications
  As a user
  I want to be able to get application information with existing roles
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: get groups and their members
  As an admin
  I want to be able to get groups
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: get users
  As an admin
  I want to be able to retrieve user information
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: get user's own information
  As user
  I want to be able to retrieve my own information
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: remove a user from a group
  As an admin
  I want to be able to remove a user from a group
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Change data of space
  As a user with space admin rights
  I want to be able to change the meta-data of a created space (increase the quota, change name, etc.)
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Disabling and deleting space
  As a manager of space
  I want to be able to disable the space first, then delete it.
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Download file in project space
  As a user with different role
  I want to be able to download files
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: A manager of the space can edit public link
  As an user with manager space role
  I want to be able to edit a public link.
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Preview file in project space
  As a user
  I want to be able to download different files for the preview
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: List and create spaces
  As a user
  I want to be able to list project spaces
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Notification
  As a user
  I want to be notified of actions related to me
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: public link for a space

  Background:
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: State of the quota
  As a user
  I want to be able to see the state of the quota
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Remove files, folder
  As a user
  I want to be able to remove files, folders
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Resharing
  As a user
  I want to reshare resources
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Restore files, folder
  As a user with manager and editor role
  I want to be able to restore files, folders
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Restoring space
  As a manager of space
  I want to be able to restore a disabled space
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Search
  As a user 
  I want to search for resources in the space
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Space management
  As a user with space admin permission
  I want to be able to manage all existing project spaces
@@ -1,4 +1,4 @@
-@api @skipOnOcV10 @skipOnStable2.0
+@api @skipOnStable2.0
 Feature: Tag
  As a user 
  I want to tag resources 
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: upload resources using TUS protocol
  As a user
  I want to be able to upload files
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Upload files into a space
  As a user
  I want to be able to create folders and files in the space
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: change shared resource
  As a user 
  I want to change the shared resource
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: checksums
  As a user
  I want to upload files with checksum
@@ -10,7 +10,7 @@ Feature: checksums
    And using spaces DAV path
    And user "Brian" has been created with default attributes and without skeleton files

-  @files_sharing-app-required @issue-1291
+  @issue-1291
  Scenario: sharing a file with checksum should return the checksum in the propfind using new DAV path
    Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
    And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
@@ -19,7 +19,7 @@ Feature: checksums
    Then the HTTP status code should be "207"
    And the webdav checksum should match "SHA1:3ee962b839762adb0ad8ba6023a4690be478de6f MD5:d70b40f177b14b470d1756a3c12b963a ADLER32:8ae90960"

-  @files_sharing-app-required @issue-1291
+  @issue-1291
  Scenario: modifying a shared file should return correct checksum in the propfind using new DAV path
    Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
    And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: copy file
  As a user
  I want to be able to copy files
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: create file or folder named similar to Shares folder
  As a user
  I want to be able to create files and folders when the Shares folder exists
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: favorite
  As a user
  I want to favorite resources
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: move (rename) file
  As a user
  I want to be able to move and rename files
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Public can download folders from project space public link
  As a public
  I want to be able to download folder from public link
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: sharing
  As a user
  I want to share resources with different permissions
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Share spaces
  As the owner of a space
  I want to be able to add members to a space, and to remove access for them
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Share spaces via link
  As the manager of a space
  I want to be able to share a space via public link
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Share a file or folder that is inside a space
  As a user with manager space role
  I want to be able to share the data inside the space
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: Share a file or folder that is inside a space via public link
  As a user with manager space role
  I want to be able to share the data inside the space via public link
@@ -1,4 +1,4 @@
-@api @skipOnOcV10
+@api 
 Feature: upload resources on share using TUS protocol
  As a user
  I want to be able to upload files
@@ -1867,40 +1867,6 @@ class FeatureContext extends BehatVariablesContext {
 		);
 	}

-	/**
-	 * @Given file :filename with text :text has been created in local storage on the server
-	 *
-	 * @param string $filename
-	 * @param string $text
-	 *
-	 * @return void
-	 * @throws Exception
-	 */
-	public function fileHasBeenCreatedInLocalStorageWithText(string $filename, string $text): void {
-		$this->createFileOnServerWithContent(
-			LOCAL_STORAGE_DIR_ON_REMOTE_SERVER . "/$filename",
-			$text
-		);
-	}
-
-	/**
-	 * @Given file :filename has been deleted from local storage on the server
-	 *
-	 * @param string $filename
-	 *
-	 * @return void
-	 * @throws Exception
-	 */
-	public function fileHasBeenDeletedInLocalStorage(string $filename): void {
-		SetupHelper::deleteFileOnServer(
-			LOCAL_STORAGE_DIR_ON_REMOTE_SERVER . "/$filename",
-			$this->getStepLineRef(),
-			$this->getBaseUrl(),
-			$this->getAdminUsername(),
-			$this->getAdminPassword()
-		);
-	}
-
 	/**
 	 * @param string $user
 	 *
@@ -2185,83 +2151,6 @@ class FeatureContext extends BehatVariablesContext {
 		$this->response = $this->getStatusPhp();
 	}

-	/**
-	 * @When the administrator creates file :path with content :content in local storage using the testing API
-	 *
-	 * @param string $path
-	 * @param string $content
-	 *
-	 * @return void
-	 */
-	public function theAdministratorCreatesFileUsingTheTestingApi(string $path, string $content): void {
-		$this->theAdministratorCreatesFileWithContentInLocalStorageUsingTheTestingApi(
-			$path,
-			$content,
-			'local_storage'
-		);
-	}
-
-	/**
-	 * @Given the administrator has created file :path with content :content in local storage using the testing API
-	 *
-	 * @param string $path
-	 * @param string $content
-	 *
-	 * @return void
-	 */
-	public function theAdministratorHasCreatedFileUsingTheTestingApi(string $path, string $content): void {
-		$this->theAdministratorHasCreatedFileWithContentInLocalStorageUsingTheTestingApi(
-			$path,
-			$content,
-			'local_storage'
-		);
-	}
-
-	/**
-	 * @When the administrator creates file :path with content :content in local storage :mountPoint using the testing API
-	 *
-	 * @param string $path
-	 * @param string $content
-	 * @param string $mountPoint
-	 *
-	 * @return void
-	 * @throws Exception
-	 */
-	public function theAdministratorCreatesFileWithContentInLocalStorageUsingTheTestingApi(
-		string $path,
-		string $content,
-		string $mountPoint
-	): void {
-		$response = $this->copyContentToFileInTemporaryStorageOnSystemUnderTest(
-			"$mountPoint/$path",
-			$content
-		);
-		$this->setResponse($response);
-	}
-
-	/**
-	 * @Given the administrator has created file :path with content :content in local storage :mountPoint
-	 *
-	 * @param string $path
-	 * @param string $content
-	 * @param string $mountPoint
-	 *
-	 * @return void
-	 * @throws Exception
-	 */
-	public function theAdministratorHasCreatedFileWithContentInLocalStorageUsingTheTestingApi(
-		string $path,
-		string $content,
-		string $mountPoint
-	): void {
-		$this->theAdministratorCreatesFileWithContentInLocalStorageUsingTheTestingApi(
-			$path,
-			$content,
-			$mountPoint
-		);
-		$this->theHTTPStatusCodeShouldBeSuccess();
-	}
-
 	/**
 	 * Copy a file from the test-runner to the temporary storage directory on
 	 * the system-under-test. This uses the testing app to push the file into
@@ -2321,28 +2210,6 @@ class FeatureContext extends BehatVariablesContext {
 		);
 	}

-	/**
-	 * @When the administrator deletes file :path in local storage using the testing API
-	 *
-	 * @param string $path
-	 *
-	 * @return void
-	 */
-	public function theAdministratorDeletesFileInLocalStorageUsingTheTestingApi(string $path): void {
-		$user = $this->getAdminUsername();
-		$response = OcsApiHelper::sendRequest(
-			$this->getBaseUrl(),
-			$user,
-			$this->getAdminPassword(),
-			'DELETE',
-			"/apps/testing/api/v1/file",
-			$this->getStepLineRef(),
-			['file' => LOCAL_STORAGE_DIR_ON_REMOTE_SERVER . "/$path"],
-			$this->getOcsApiVersion()
-		);
-		$this->setResponse($response);
-	}
-
 	/**
 	 * @Given a file with the size of :size bytes and the name :name has been created locally
 	 *
@@ -2612,21 +2479,6 @@ class FeatureContext extends BehatVariablesContext {
 		$this->setResponse($response);
 	}

-	/**
-	 * @When the local storage mount for :mount is renamed to :target
-	 *
-	 * @param string $mount
-	 * @param string $target
-	 *
-	 * @return void
-	 */
-	public function theLocalStorageMountForIsRenamedTo(string $mount, string $target): void {
-		$mountPath = TEMPORARY_STORAGE_DIR_ON_REMOTE_SERVER . "/" . ltrim($mount, '/');
-		$targetPath = TEMPORARY_STORAGE_DIR_ON_REMOTE_SERVER . "/" . ltrim($target, '/');
-
-		$this->moveFileInServerRoot($mountPath, $targetPath);
-	}
-
 	/**
 	 * @Then the file :path with content :content should exist in the server root
 	 *
@@ -3668,20 +3520,6 @@ class FeatureContext extends BehatVariablesContext {
 		);
 	}

-	/**
-	 * After Scenario. restore trusted servers
-	 *
-	 * @AfterScenario @federation-app-required
-	 *
-	 * @return void
-	 */
-	public function restoreTrustedServersAfterScenario(): void {
-		$this->restoreTrustedServers('LOCAL');
-		if ($this->federatedServerExists()) {
-			$this->restoreTrustedServers('REMOTE');
-		}
-	}
-
 	/**
 	 * @param string $sourceUser
 	 * @param string $targetUser
@@ -3817,21 +3655,6 @@ class FeatureContext extends BehatVariablesContext {
 		return $body;
 	}

-	/**
-	 * Before Scenario to Save trusted Servers
-	 *
-	 * @BeforeScenario @federation-app-required
-	 *
-	 * @return void
-	 * @throws Exception
-	 */
-	public function setInitialTrustedServersBeforeScenario(): void {
-		$this->initialTrustedServer = [
-			'LOCAL' => $this->getTrustedServers(),
-			'REMOTE' => $this->getTrustedServers('REMOTE')
-		];
-	}
-
 	/**
 	 * The method returns userId
 	 *
@@ -91,9 +91,3 @@ if (!\defined('ACCEPTANCE_TEST_DIR_ON_REMOTE_SERVER')) {
 if (!\defined('TEMPORARY_STORAGE_DIR_ON_REMOTE_SERVER')) {
 	\define('TEMPORARY_STORAGE_DIR_ON_REMOTE_SERVER', ACCEPTANCE_TEST_DIR_ON_REMOTE_SERVER . '/server_tmp');
 }
-
-// The following directory is created, used, and deleted by tests that need to
-// use some "local external storage" on the server.
-if (!\defined('LOCAL_STORAGE_DIR_ON_REMOTE_SERVER')) {
-	\define('LOCAL_STORAGE_DIR_ON_REMOTE_SERVER', TEMPORARY_STORAGE_DIR_ON_REMOTE_SERVER . '/local_storage');
-}
@@ -12,7 +12,7 @@ Feature: auth
    When a user requests "/remote.php/webdav" with "PROPFIND" and no authentication
    Then the HTTP status code should be "401"

-  @smokeTest @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: using spaces WebDAV anonymously
    When user "Alice" requests "/dav/spaces/%spaceid%" with "PROPFIND" and no authentication
    Then the HTTP status code should be "401"
@@ -25,7 +25,7 @@ Feature: auth
      | dav_path           |
      | /remote.php/webdav |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_path              |
      | /dav/spaces/%spaceid% |
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: auth
  As a user
  I want to send delete request with wrong password
@@ -7,7 +7,7 @@ Feature: auth
  Background:
    Given user "another-admin" has been created with default attributes and without skeleton files

-  @smokeTest @issue-1337 @issue-1319 @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest @issue-1337 @issue-1319
  Scenario: send DELETE requests to OCS endpoints as admin with wrong password
    Given user "another-admin" has been added to group "admin"
    When user "another-admin" requests these endpoints with "DELETE" using password "invalid" about user "Alice"
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: auth
  As a user
  I want to send GET request to various endpoints
@@ -72,7 +72,7 @@ Feature: auth
    Then the HTTP status code of responses on all endpoints should be "401"
    And the OCS status code of responses on all endpoints should be "401"

-  @issue-1338 @issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @issue-1338 @issue-1337 @smokeTest
  Scenario: using OCS as normal user with wrong password
    When user "Alice" requests these endpoints with "GET" using password "invalid"
      | endpoint                                                    |
@@ -120,7 +120,7 @@ Feature: auth
    Then the HTTP status code of responses on all endpoints should be "200"
    And the OCS status code of responses on all endpoints should be "200"

-  @issue-1337 @issue-1319 @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @issue-1337 @issue-1319
  Scenario: using OCS as admin user with wrong password
    Given user "another-admin" has been created with default attributes and without skeleton files
    And user "another-admin" has been added to group "admin"
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: auth
  As a user
  I want to send POST request to various endpoints
@@ -7,7 +7,7 @@ Feature: auth
  Background:
    Given user "Alice" has been created with default attributes and without skeleton files

-  @issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @issue-1337 @smokeTest
  Scenario: send POST requests to OCS endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                                        |
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: auth
  As a user
  I want to send PUT request to various endpoints
@@ -7,7 +7,7 @@ Feature: auth
  Background:
    Given user "another-admin" has been created with default attributes and without skeleton files

-  @issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @issue-1337 @smokeTest
  Scenario: send PUT request to OCS endpoints as admin with wrong password
    Given user "another-admin" has been added to group "admin"
    When user "another-admin" requests these endpoints with "PUT" including body "doesnotmatter" using password "invalid" about user "Alice"
@@ -14,7 +14,7 @@ Feature: COPY file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send COPY requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "COPY" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -25,7 +25,7 @@ Feature: COPY file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send COPY requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "COPY" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -34,7 +34,7 @@ Feature: COPY file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send COPY requests to webDav endpoints as normal user with no password
    When user "Alice" requests these endpoints with "COPY" using password "" about user "Alice"
      | endpoint                                           |
@@ -45,7 +45,7 @@ Feature: COPY file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send COPY requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "COPY" using password "" about user "Alice"
      | endpoint                                           |
@@ -63,7 +63,7 @@ Feature: COPY file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "403"

- @skipOnOcV10 @personalSpace
+ @personalSpace
 Scenario: send COPY requests to another user's webDav endpoints as normal user using the spaces WebDAV API
   When user "Brian" requests these endpoints with "COPY" about user "Alice"
     | endpoint                                           |
@@ -83,7 +83,7 @@ Feature: COPY file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send COPY requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "COPY" using the password of user "Alice"
      | endpoint                                           |
@@ -103,7 +103,7 @@ Feature: COPY file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send COPY requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "COPY" using the password of user "Alice"
      | endpoint                                           |
@@ -112,7 +112,7 @@ Feature: COPY file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send COPY requests to webDav endpoints without any authentication
    When a user requests these endpoints with "COPY" with no authentication about user "Alice"
      | endpoint                                           |
@@ -123,7 +123,7 @@ Feature: COPY file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send COPY requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "COPY" with no authentication about user "Alice"
      | endpoint                                           |
@@ -132,7 +132,7 @@ Feature: COPY file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10
+  
  Scenario: send COPY requests to webDav endpoints with body as normal user
    When user "Alice" requests these endpoints with "COPY" including body "doesnotmatter" about user "Alice"
      | endpoint                                           |
@@ -144,7 +144,7 @@ Feature: COPY file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "415"

- @skipOnOcV10 @personalSpace
+ @personalSpace
  Scenario: send COPY requests to webDav endpoints with body as normal user using the spaces WebDAV API
    When user "Alice" requests these endpoints with "COPY" including body "doesnotmatter" about user "Alice"
      | endpoint                                           |
@@ -15,7 +15,7 @@ Feature: delete file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send DELETE requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "DELETE" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -27,7 +27,7 @@ Feature: delete file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send DELETE requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "DELETE" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -48,7 +48,7 @@ Feature: delete file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send DELETE requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "DELETE" using password "" about user "Alice"
      | endpoint                                           |
@@ -66,7 +66,7 @@ Feature: delete file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "404"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send DELETE requests to another user's webDav endpoints as normal user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "DELETE" about user "Alice"
      | endpoint                                           |
@@ -86,7 +86,7 @@ Feature: delete file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send DELETE requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "DELETE" using the password of user "Alice"
      | endpoint                                           |
@@ -106,7 +106,7 @@ Feature: delete file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send DELETE requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "DELETE" using the password of user "Alice"
      | endpoint                                           |
@@ -115,7 +115,7 @@ Feature: delete file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send DELETE requests to webDav endpoints without any authentication
    When a user requests these endpoints with "DELETE" with no authentication about user "Alice"
      | endpoint                                           |
@@ -126,7 +126,7 @@ Feature: delete file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send DELETE requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "DELETE" with no authentication about user "Alice"
      | endpoint                                           |
@@ -135,7 +135,7 @@ Feature: delete file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10
+  
  Scenario: send DELETE requests to webDav endpoints with body as normal user
    When user "Alice" requests these endpoints with "DELETE" including body "doesnotmatter" about user "Alice"
      | endpoint                                           |
@@ -146,7 +146,7 @@ Feature: delete file/folder
      | /remote.php/dav/files/%username%/FOLDER            |
    Then the HTTP status code of responses on all endpoints should be "415"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send DELETE requests to webDav endpoints with body as normal user using the spaces WebDAV API
    When user "Alice" requests these endpoints with "DELETE" including body "doesnotmatter" about user "Alice"
      | endpoint                                           |
@@ -15,7 +15,7 @@ Feature: LOCK file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send LOCK requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -26,7 +26,7 @@ Feature: LOCK file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send LOCK requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -35,7 +35,7 @@ Feature: LOCK file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send LOCK requests to webDav endpoints as normal user with no password
    When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -46,7 +46,7 @@ Feature: LOCK file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send LOCK requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -90,7 +90,7 @@ Feature: LOCK file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send LOCK requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "LOCK" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -110,7 +110,7 @@ Feature: LOCK file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send LOCK requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "LOCK" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -119,7 +119,7 @@ Feature: LOCK file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send LOCK requests to webDav endpoints without any authentication
    When a user requests these endpoints with "LOCK" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -130,7 +130,7 @@ Feature: LOCK file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send LOCK requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "LOCK" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -11,7 +11,7 @@ Feature: create folder using MKCOL
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send MKCOL requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -22,7 +22,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send MKCOL requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -31,7 +31,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send MKCOL requests to webDav endpoints as normal user with no password
    When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -42,7 +42,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnOcV10 @personalSpace @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest @personalSpace
  Scenario: send MKCOL requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -51,7 +51,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @issue-5049 @issue-1347 @issue-1292
+  @issue-5049 @issue-1347 @issue-1292
  Scenario: send MKCOL requests to another user's webDav endpoints as normal user
    Given user "Brian" has been created with default attributes and without skeleton files
    When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice"
@@ -62,7 +62,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "404"

-  @skipOnOcV10 @issue-5049 @issue-1347 @issue-1292
+  @issue-5049 @issue-1347 @issue-1292
  Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user
    Given user "Brian" has been created with default attributes and without skeleton files
    When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user"
@@ -84,7 +84,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "404"

-  @skipOnOcV10 @issue-5049 @personalSpace @issue-1347 @issue-1292
+  @issue-5049 @personalSpace @issue-1347 @issue-1292
  Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user using the spaces WebDAV API
    Given user "Brian" has been created with default attributes and without skeleton files
    When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user"
@@ -106,7 +106,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MKCOL requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "MKCOL" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -127,7 +127,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MKCOL requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    Given user "Brian" has been created with default attributes and without skeleton files
    When user "Brian" requests these endpoints with "MKCOL" including body "doesnotmatter" using the password of user "Alice"
@@ -137,7 +137,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send MKCOL requests to webDav endpoints without any authentication
    When a user requests these endpoints with "MKCOL" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -148,7 +148,7 @@ Feature: create folder using MKCOL
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send MKCOL requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "MKCOL" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -14,7 +14,7 @@ Feature: MOVE file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send MOVE requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "MOVE" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -25,7 +25,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send MOVE requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "MOVE" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -34,7 +34,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send MOVE requests to webDav endpoints as normal user with no password
    When user "Alice" requests these endpoints with "MOVE" using password "" about user "Alice"
      | endpoint                                           |
@@ -45,7 +45,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send MOVE requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "MOVE" using password "" about user "Alice"
      | endpoint                                           |
@@ -63,7 +63,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "403"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MOVE requests to another user's webDav endpoints as normal user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "MOVE" about user "Alice"
      | endpoint                                           |
@@ -83,7 +83,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MOVE requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "MOVE" using the password of user "Alice"
      | endpoint                                           |
@@ -103,7 +103,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MOVE requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "MOVE" using the password of user "Alice"
      | endpoint                                           |
@@ -112,7 +112,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send MOVE requests to webDav endpoints without any authentication
    When a user requests these endpoints with "MOVE" with no authentication about user "Alice"
      | endpoint                                           |
@@ -123,7 +123,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send MOVE requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "MOVE" with no authentication about user "Alice"
      | endpoint                                           |
@@ -132,7 +132,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10
+  
  Scenario: send MOVE requests to webDav endpoints with body as normal user
    When user "Alice" requests these endpoints with "MOVE" including body "doesnotmatter" about user "Alice"
      | endpoint                                           |
@@ -144,7 +144,7 @@ Feature: MOVE file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "415"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MOVE requests to webDav endpoints with body as normal user using the spaces WebDAV API
    When user "Alice" requests these endpoints with "MOVE" including body "doesnotmatter" about user "Alice"
      | endpoint                                           |
@@ -15,7 +15,7 @@ Feature: POST file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send POST requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -26,7 +26,7 @@ Feature: POST file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send POST requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -35,7 +35,7 @@ Feature: POST file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send POST requests to webDav endpoints as normal user with no password
    When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -46,7 +46,7 @@ Feature: POST file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send POST requests to webDav endpoints as normal user with no password  using the spaces WebDAV API
    When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -64,7 +64,7 @@ Feature: POST file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "404"

-  @skipOnOcV10 @personalSpace @issue-1287
+  @personalSpace @issue-1287
  Scenario: send POST requests to another user's webDav endpoints as normal user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "POST" including body "doesnotmatter" about user "Alice"
      | endpoint                                           |
@@ -84,7 +84,7 @@ Feature: POST file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send POST requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "POST" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -104,7 +104,7 @@ Feature: POST file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send POST requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "POST" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -113,7 +113,7 @@ Feature: POST file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send POST requests to webDav endpoints without any authentication
    When a user requests these endpoints with "POST" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -124,7 +124,7 @@ Feature: POST file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send POST requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "POST" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -14,7 +14,7 @@ Feature: PROPFIND file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send PROPFIND requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -25,7 +25,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PROPFIND requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -34,7 +34,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send PROPFIND requests to webDav endpoints as normal user with no password
    When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -45,7 +45,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PROPFIND requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -63,7 +63,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "404"

-  @skipOnOcV10 @personalSpace @issue-1347
+  @personalSpace @issue-1347
  Scenario: send PROPFIND requests to another user's webDav endpoints as normal user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "PROPFIND" to get property "d:getetag" about user "Alice"
      | endpoint                                           |
@@ -83,7 +83,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PROPFIND requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "PROPFIND" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -103,7 +103,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PROPFIND requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "PROPFIND" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -112,7 +112,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send PROPFIND requests to webDav endpoints without any authentication
    When a user requests these endpoints with "PROPFIND" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -123,7 +123,7 @@ Feature: PROPFIND file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PROPFIND requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "PROPFIND" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -15,7 +15,7 @@ Feature: PROPPATCH file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send PROPPATCH requests to webDav endpoints as normal user with wrong password
    When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -26,7 +26,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PROPPATCH requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -35,7 +35,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send PROPPATCH requests to webDav endpoints as normal user with no password
    When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -46,7 +46,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PROPPATCH requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -64,7 +64,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "404"

-  @issue-1347 @issue-1292 @skipOnOcV10 @personalSpace
+  @issue-1347 @issue-1292 @personalSpace
  Scenario: send PROPPATCH requests to another user's webDav endpoints as normal user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "PROPPATCH" to set property "favorite" about user "Alice"
      | endpoint                                           |
@@ -84,7 +84,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PROPPATCH requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -104,7 +104,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PROPPATCH requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -113,7 +113,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send PROPPATCH requests to webDav endpoints without any authentication
    When a user requests these endpoints with "PROPPATCH" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -124,7 +124,7 @@ Feature: PROPPATCH file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PROPPATCH requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "PROPPATCH" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -15,7 +15,7 @@ Feature: PUT file/folder
    And user "Alice" has created folder "/FOLDER"
    And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  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                                           |
@@ -26,7 +26,7 @@ Feature: PUT file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PUT requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "invalid" about user "Alice"
      | endpoint                                           |
@@ -35,7 +35,7 @@ Feature: PUT file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  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                                           |
@@ -46,7 +46,7 @@ Feature: PUT file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PUT requests to webDav endpoints as normal user with no password using the spaces WebDAV API
    When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "" about user "Alice"
      | endpoint                                           |
@@ -55,7 +55,7 @@ Feature: PUT file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10
+  
  Scenario: send PUT requests to another user's webDav endpoints as normal user
    When user "Brian" requests these endpoints with "PUT" including body "doesnotmatter" about user "Alice"
      | endpoint                                       |
@@ -67,7 +67,7 @@ Feature: PUT file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "403"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PUT requests to another user's webDav endpoints as normal user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "PUT" including body "doesnotmatter" about user "Alice"
      | endpoint                                       |
@@ -90,7 +90,7 @@ Feature: PUT file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PUT requests to webDav endpoints using invalid username but correct password using the spaces WebDAV API
    When user "usero" requests these endpoints with "PUT" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -110,7 +110,7 @@ Feature: PUT file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PUT requests to webDav endpoints using valid password and username of different user using the spaces WebDAV API
    When user "Brian" requests these endpoints with "PUT" including body "doesnotmatter" using the password of user "Alice"
      | endpoint                                           |
@@ -119,7 +119,7 @@ Feature: PUT file/folder
      | /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
+  @smokeTest
  Scenario: send PUT requests to webDav endpoints without any authentication
    When a user requests these endpoints with "PUT" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -130,7 +130,7 @@ Feature: PUT file/folder
      | /remote.php/dav/files/%username%/PARENT/parent.txt |
    Then the HTTP status code of responses on all endpoints should be "401"

-  @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @skipOnOcV10 @personalSpace
+  @smokeTest @personalSpace
  Scenario: send PUT requests to webDav endpoints without any authentication using the spaces WebDAV API
    When a user requests these endpoints with "PUT" with body "doesnotmatter" and no authentication about user "Alice"
      | endpoint                                           |
@@ -1,4 +1,4 @@
-@api @skipOnOcV10.10.0
+@api
 Feature: make webdav request with special urls
  As a user
  I want to make webdav request with special urls
@@ -23,7 +23,7 @@ Feature: make webdav request with special urls
      | //remote.php/dav//files/%username%//FOLDER          |
    Then the HTTP status code of responses on all endpoints should be "204"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send DELETE requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When user "Alice" requests these endpoints with "DELETE" using password "%regular%" about user "Alice"
      | endpoint                                             |
@@ -44,7 +44,7 @@ Feature: make webdav request with special urls
      | //remote.php/dav//files/%username%//FOLDER          |
    Then the HTTP status code of responses on all endpoints should be "200"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send GET requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When user "Alice" requests these endpoints with "GET" using password "%regular%" about user "Alice"
      | endpoint                                             |
@@ -65,7 +65,7 @@ Feature: make webdav request with special urls
      | //remote.php/dav//files/%username%//FOLDER          |
    Then the HTTP status code of responses on all endpoints should be "200"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send LOCK requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When the user "Alice" requests these endpoints with "LOCK" to get property "d:shared" with password "%regular%" about user "Alice"
      | endpoint                                             |
@@ -87,7 +87,7 @@ Feature: make webdav request with special urls
      | /remote.php/dav//files/%username%/PARENT6  |
    Then the HTTP status code of responses on all endpoints should be "201"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MKCOL requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When user "Alice" requests these endpoints with "MKCOL" using password "%regular%" about user "Alice"
      | endpoint                                   |
@@ -110,7 +110,7 @@ Feature: make webdav request with special urls
      | /remote.php/dav//files/%username%/PARENT2/parent.txt | /remote.php/dav/files/%username%/PARENT2/parent1.txt |
    Then the HTTP status code of responses on all endpoints should be "201"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send MOVE requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When user "Alice" requests these endpoints with "MOVE" using password "%regular%" about user "Alice"
      | endpoint                                             | destination                                          |
@@ -131,7 +131,7 @@ Feature: make webdav request with special urls
      | //remote.php/dav//files/%username%//FOLDER          |
    Then the HTTP status code of responses on all endpoints should be "500" or "501"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send POST requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "%regular%" about user "Alice"
      | endpoint                                            |
@@ -152,7 +152,7 @@ Feature: make webdav request with special urls
      | //remote.php/dav//files/%username%//FOLDER           |
    Then the HTTP status code of responses on all endpoints should be "207"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PROPFIND requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When the user "Alice" requests these endpoints with "PROPFIND" to get property "d:href" with password "%regular%" about user "Alice"
      | endpoint                                            |
@@ -173,7 +173,7 @@ Feature: make webdav request with special urls
      | //remote.php/dav//files/%username%//FOLDER           |
    Then the HTTP status code of responses on all endpoints should be "207"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PROPPATCH requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When the user "Alice" requests these endpoints with "PROPPATCH" to set property "d:getlastmodified" with password "%regular%" about user "Alice"
      | endpoint                                            |
@@ -194,7 +194,7 @@ Feature: make webdav request with special urls
      | //remote.php/dav/files/%username%/PARENT//parent.txt |
    Then the HTTP status code of responses on all endpoints should be "204" or "201"

-  @skipOnOcV10 @personalSpace
+  @personalSpace
  Scenario: send PUT requests to webDav endpoints with 2 slashes using the spaces WebDAV API
    When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "%regular%" about user "Alice"
      | endpoint                                             |
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: capabilities
  As an admin
  I want to list the capabilities
@@ -54,7 +54,7 @@ Feature: capabilities
    }
    """

-  @files_trashbin-app-required @skipOnReva
+  @skipOnReva
  Scenario: getting trashbin app capability with admin user
    When the administrator retrieves the capabilities using the capabilities API
    Then the OCS status code should be "100"
@@ -93,7 +93,7 @@ Feature: capabilities
    }
    """

-  @files_versions-app-required @skipOnReva
+ @skipOnReva
  Scenario: getting versions app capability with admin user
    When the administrator retrieves the capabilities using the capabilities API
    Then the OCS status code should be "100"
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: default capabilities for normal user
  As a user
  I want to list capabilities
@@ -32,7 +32,7 @@ Feature: favorite
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -54,7 +54,7 @@ Feature: favorite
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -75,7 +75,7 @@ Feature: favorite
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -97,7 +97,7 @@ Feature: favorite
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -118,7 +118,7 @@ Feature: favorite
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -145,7 +145,7 @@ Feature: favorite
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -222,7 +222,7 @@ Feature: favorite
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: favorite
  As a user
  I want to favorite the shared resources
@@ -16,7 +16,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -32,7 +32,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -49,7 +49,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -66,7 +66,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -84,7 +84,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -102,7 +102,7 @@ Feature: checksums
      | dav_version |
      | old         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -120,7 +120,7 @@ Feature: checksums
      | dav_version |
      | old         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -138,7 +138,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -154,7 +154,7 @@ Feature: checksums
      | dav_version |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -170,12 +170,12 @@ Feature: checksums
      | dav_version |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |

-  @files_sharing-app-required @issue-1291
+  @issue-1291
  Scenario Outline: sharing a file with checksum should return the checksum in the propfind using new DAV path
    Given auto-accept shares has been disabled
    And using <dav_version> DAV path
@@ -190,7 +190,7 @@ Feature: checksums
      | dav_version |
      | new         |

-  @files_sharing-app-required @issue-1291 @skipOnOcV10
+  @issue-1291
  Scenario Outline: modifying a shared file should return correct checksum in the propfind using new DAV path
    Given auto-accept shares has been disabled
    And using <dav_version> DAV path
@@ -217,7 +217,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -232,7 +232,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -251,7 +251,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -268,7 +268,7 @@ Feature: checksums
      | dav_version |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -292,7 +292,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -315,7 +315,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -333,7 +333,7 @@ Feature: checksums
      | old         |
      | new         |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version |
      | spaces      |
@@ -356,7 +356,7 @@ Feature: checksums
      | new         | " oc?test=ab&cd " |
      | new         | "# %ab ab?=ed"    |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav_version | renamed_file      |
      | spaces      | " oc?test=ab&cd " |
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: Sharing resources with different case names with the sharee and checking the coexistence of resources on sharee/receivers side
  As a user
  I want to share resources with case sensitive names
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: resources shared with the same name are received with unique names
  As a user
  I want to share resources with same name
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-1327
+@api @issue-1327
 Feature: shares are received in the default folder for received shares
  As a user
  I want to share the default Shares folder
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: sharing works when a username and group name are the same
  As a user
  I want to share resources with group and users having same name
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: share resources where the sharee receives the share in multiple ways
  As a user
  I want to receives the same resource share from multiple channels
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-1328
+@api @issue-1328
 Feature: share resources with a disabled user
  As a user
  I want to share resources to disabled user
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: cannot share resources with invalid permissions
  As a user
  I want to share resources with invalid permission
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: sharing
  As a user
  I want to share resources to others
@@ -525,7 +525,7 @@ Feature: sharing
    And file "/textfile0.txt" should not be included as path in the response
    And as "Brian" file "/Shares/textfile0.txt" should not exist
    And as "Carol" file "/Shares/textfile0.txt" should not exist
-    @skipOnOcV10 @issue-2441
+    @issue-2441
    Examples:
      | ocs_api_version | ocs_status_code | path           |
      | 1               | 100             | /textfile0.txt |
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-1328 @issue-1289
+@api @issue-1328 @issue-1289
 Feature: sharing
  As a user
  I want to delete shares
@@ -61,7 +61,7 @@ Feature: sharing
      | pending_share_path |
      | /sub               |

-  @smokeTest @files_trashbin-app-required
+  @smokeTest
  Scenario: deleting a file out of a share as recipient creates a backup for the owner
    Given using OCS API version "1"
    And user "Alice" has created folder "/shared"
@@ -75,7 +75,7 @@ Feature: sharing
    And as "Alice" file "/shared_file.txt" should exist in the trashbin
    And as "Brian" file "/shared_file.txt" should exist in the trashbin

-  @files_trashbin-app-required
+ 
  Scenario: deleting a folder out of a share as recipient creates a backup for the owner
    Given using OCS API version "1"
    And user "Alice" has created folder "/shared"
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-1289 @issue-1328
+@api @issue-1289 @issue-1328
 Feature: accept/decline shares coming from internal users
  As a user
  I want to have control of which received shares I accept
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: accept/decline shares coming from internal users to the Shares folder
  As a user
  I want to have control of which received shares I accept
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-1328 @issues-1289
+@api @issue-1328 @issues-1289
 Feature: sharing

  Background:
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-1289 @issue-1328
+@api @issue-1289 @issue-1328
 Feature: sharing

  Background:
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: moving a share inside another share
  As a user
  I want to move a shared resource inside another shared resource
@@ -54,7 +54,7 @@ Feature: moving a share inside another share
    And as "Alice" file "/folderA/localFolder/localFile.txt" should exist
    And as "Brian" file "/Shares/folderA/localFolder/localFile.txt" should exist

-  @skipOnOcV10
+  
  Scenario: share receiver tries to move a whole share inside a local folder
    Given user "Brian" has created folder "localFolder"
    And user "Brian" has uploaded file with content "local text" to "/localFolder/localFile.txt"
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: sharing

  Background:
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-1289 @issue-1328
+@api @issue-1289 @issue-1328
 Feature: sharing

  Background:
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: sharing

  Background:
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: get the pending shares filtered by type (user, group etc)
  As a user
  I want to be able to know the pending shares that I have received of a particular type (user, group etc)
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: get the received shares filtered by type (user, group etc)
  As a user
  I want to be able to know the shares that I have received of a particular type (user, group etc)
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: get the received shares filtered by type (user, group etc)
  As a user
  I want to be able to know the shares that I have received of a particular type (user, group etc)
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: get shares filtered by type (user, group etc)
  As a user
  I want to be able to know the shares that I have made of a particular type (user, group etc)
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: get shares filtered by type (user, group etc)
  As a user
  I want to be able to know the shares that I have made of a particular type (user, group etc)
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: sharing

  Background:
@@ -23,7 +23,7 @@ Feature: sharing
      | old      |
      | new      |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav-path |
      | spaces   |
@@ -154,7 +154,7 @@ Feature: sharing
      | old      |
      | new      |

-    @skipOnOcV10 @personalSpace
+    @personalSpace
    Examples:
      | dav-path |
      | spaces   |
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: share access by ID

  Background:
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api
 Feature: sharing

  Background:
--- a/Show More
+++ b/Show More