From 7c548a5c07d2824e73ff5c3354c6c1cf20b68d3c Mon Sep 17 00:00:00 2001 From: Prajwol Amatya Date: Tue, 24 Dec 2024 15:52:09 +0545 Subject: [PATCH] run flaky tests --- .drone.star | 75 +- .../test.feature | 2277 +++++++++++++++++ 2 files changed, 2312 insertions(+), 40 deletions(-) create mode 100644 tests/acceptance/features/coreApiShareOperationsToShares2/test.feature diff --git a/.drone.star b/.drone.star index 2b9be9b12ea..d967c38153e 100644 --- a/.drone.star +++ b/.drone.star @@ -69,13 +69,13 @@ OCIS_FED_DOMAIN = "%s:10200" % FED_OCIS_SERVER_NAME # configuration config = { "cs3ApiTests": { - "skip": False, + "skip": True, }, "wopiValidatorTests": { - "skip": False, + "skip": True, }, "k6LoadTests": { - "skip": False, + "skip": True, }, "localApiTests": { "basic": { @@ -89,52 +89,52 @@ config = { "apiLocks", "apiActivities", ], - "skip": False, + "skip": True, }, "graph": { "suites": [ "apiGraph", "apiServiceAvailability", ], - "skip": False, + "skip": True, "withRemotePhp": [True], }, "graphUserGroup": { "suites": [ "apiGraphUserGroup", ], - "skip": False, + "skip": True, "withRemotePhp": [True], }, "spaces": { "suites": [ "apiSpaces", ], - "skip": False, + "skip": True, }, "spacesShares": { "suites": [ "apiSpacesShares", ], - "skip": False, + "skip": True, }, "spacesDavOperation": { "suites": [ "apiSpacesDavOperation", ], - "skip": False, + "skip": True, }, "search1": { "suites": [ "apiSearch1", ], - "skip": False, + "skip": True, }, "search2": { "suites": [ "apiSearch2", ], - "skip": False, + "skip": True, }, "sharingNg": { "suites": [ @@ -142,23 +142,23 @@ config = { "apiSharingNg1", "apiSharingNg2", ], - "skip": False, + "skip": True, }, "sharingNgShareInvitation": { "suites": [ "apiSharingNgShareInvitation", ], - "skip": False, + "skip": True, }, "sharingNgLinkShare": { "suites": [ "apiSharingNgLinkSharePermission", "apiSharingNgLinkShareRoot", ], - "skip": False, + "skip": True, }, "accountsHashDifficulty": { - "skip": False, + "skip": True, "suites": [ "apiAccountsHashDifficulty", ], @@ -168,7 +168,7 @@ config = { "suites": [ "apiNotification", ], - "skip": False, + "skip": True, "withRemotePhp": [True], "emailNeeded": True, "extraEnvironment": { @@ -188,7 +188,7 @@ config = { "suites": [ "apiAntivirus", ], - "skip": False, + "skip": True, "antivirusNeeded": True, "extraServerEnvironment": { "ANTIVIRUS_SCANNER_TYPE": "clamav", @@ -203,14 +203,14 @@ config = { "suites": [ "apiSearchContent", ], - "skip": False, + "skip": True, "tikaNeeded": True, }, "ocm": { "suites": [ "apiOcm", ], - "skip": False, + "skip": True, "withRemotePhp": [True], "federationServer": True, "emailNeeded": True, @@ -236,7 +236,7 @@ config = { "suites": [ "apiCollaboration", ], - "skip": False, + "skip": True, "collaborationServiceNeeded": True, "extraServerEnvironment": { "GATEWAY_GRPC_ADDR": "0.0.0.0:9142", @@ -246,7 +246,7 @@ config = { "suites": [ "apiAuthApp", ], - "skip": False, + "skip": True, "withRemotePhp": [True], "extraServerEnvironment": { "OCIS_ADD_RUN_SERVICES": "auth-app", @@ -257,7 +257,7 @@ config = { "suites": [ "cliCommands", ], - "skip": False, + "skip": True, "withRemotePhp": [True], "antivirusNeeded": True, "extraServerEnvironment": { @@ -269,25 +269,23 @@ config = { }, }, "apiTests": { - "numberOfParts": 7, "skip": False, - "skipExceptParts": [], }, "e2eTests": { "part": { - "skip": False, + "skip": True, "totalParts": 4, # divide and run all suites in parts (divide pipelines) "xsuites": ["search", "app-provider", "oidc", "ocm"], # suites to skip }, "search": { - "skip": False, + "skip": True, "suites": ["search"], # suites to run "tikaNeeded": True, }, }, "e2eMultiService": { "testSuites": { - "skip": False, + "skip": True, "suites": [ "smoke", "shares", @@ -310,8 +308,8 @@ config = { "dockerReleases": { "architectures": ["arm64", "amd64"], }, - "litmus": True, - "codestyle": True, + "litmus": False, + "codestyle": False, } # volume for steps to cache Go dependencies between steps of a pipeline @@ -1210,7 +1208,7 @@ def wopiValidatorTests(ctx, storage, wopiServerType, accounts_hash_difficulty = }, } -def coreApiTests(ctx, part_number = 1, number_of_parts = 1, with_remote_php = False, storage = "ocis", accounts_hash_difficulty = 4): +def coreApiTests(ctx, with_remote_php = False, storage = "ocis", accounts_hash_difficulty = 4): filterTags = "~@skipOnGraph&&~@skipOnOcis-%s-Storage" % ("OC" if storage == "owncloud" else "OCIS") test_dir = "%s/tests/acceptance" % dirs["base"] expected_failures_file = "%s/expected-failures-API-on-%s-storage.md" % (test_dir, storage.upper()) @@ -1218,7 +1216,7 @@ def coreApiTests(ctx, part_number = 1, number_of_parts = 1, with_remote_php = Fa return { "kind": "pipeline", "type": "docker", - "name": "Core-API-Tests-%s%s" % (part_number, "-withoutRemotePhp" if not with_remote_php else ""), + "name": "Core-API-Tests%s" % ("-withoutRemotePhp" if not with_remote_php else ""), "platform": { "os": "linux", "arch": "amd64", @@ -1228,16 +1226,15 @@ def coreApiTests(ctx, part_number = 1, number_of_parts = 1, with_remote_php = Fa ocisServer(storage, accounts_hash_difficulty, with_wrapper = True) + [ { - "name": "oC10ApiTests-%s" % part_number, + "name": "oC10ApiTests", "image": OC_CI_PHP % DEFAULT_PHP_VERSION, "environment": { "TEST_SERVER_URL": OCIS_URL, "OCIS_REVA_DATA_ROOT": "%s" % (dirs["ocisRevaDataRoot"] if storage == "owncloud" else ""), "SEND_SCENARIO_LINE_REFERENCES": "true", "STORAGE_DRIVER": storage, + "BEHAT_FEATURE": "tests/acceptance/features/coreApiShareOperationsToShares2/test.feature", "BEHAT_FILTER_TAGS": filterTags, - "DIVIDE_INTO_NUM_PARTS": number_of_parts, - "RUN_PART": part_number, "ACCEPTANCE_TEST_TYPE": "core-api", "EXPECTED_FAILURES_FILE": expected_failures_file, "UPLOAD_DELETE_WAIT_TIME": "1" if storage == "owncloud" else 0, @@ -1264,8 +1261,8 @@ def coreApiTests(ctx, part_number = 1, number_of_parts = 1, with_remote_php = Fa def apiTests(ctx): pipelines = [] - debugParts = config["apiTests"]["skipExceptParts"] - debugPartsEnabled = (len(debugParts) != 0) + # debugParts = config["apiTests"]["skipExceptParts"] + # debugPartsEnabled = (len(debugParts) != 0) with_remote_php = [True] if ctx.build.event == "cron" or "full-ci" in ctx.build.title.lower(): @@ -1275,10 +1272,8 @@ def apiTests(ctx): "withRemotePhp": with_remote_php, } - for runPart in range(1, config["apiTests"]["numberOfParts"] + 1): - for run_with_remote_php in defaults["withRemotePhp"]: - if (not debugPartsEnabled or (debugPartsEnabled and runPart in debugParts)): - pipelines.append(coreApiTests(ctx, runPart, config["apiTests"]["numberOfParts"], run_with_remote_php)) + for run_with_remote_php in defaults["withRemotePhp"]: + pipelines.append(coreApiTests(ctx, run_with_remote_php)) return pipelines diff --git a/tests/acceptance/features/coreApiShareOperationsToShares2/test.feature b/tests/acceptance/features/coreApiShareOperationsToShares2/test.feature new file mode 100644 index 00000000000..d4a570f05a9 --- /dev/null +++ b/tests/acceptance/features/coreApiShareOperationsToShares2/test.feature @@ -0,0 +1,2277 @@ +Feature: a + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: uploading to a user shared folder with read/write permission when the sharer has insufficient quota does not work + Given user "Alice" has been created with default attributes + And using DAV path + And user "Brian" has been created with default attributes + And user "Alice" has created folder "FOLDER" + And user "Alice" has sent the following resource share invitation: + | resource | FOLDER | + | space | Personal | + | sharee | Brian | + | shareType | user | + | permissionsRole | Editor | + And user "Brian" has a share "FOLDER" synced + And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1" + When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API + Then the HTTP status code should be "507" + And as "Alice" file "/FOLDER/myfile.txt" should not exist + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces | + + + Scenario Outline: retrieving folder quota when no quota is set + Given using OCS API version "1" + And user "Alice" has been created with default attributes + And using DAV path + When user "Admin" changes the quota of the "Alice Hansen" space to "0" + Then the HTTP status code should be "200" + And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0" + Examples: + | dav-path-version | + | old | + | new | + | spaces |