From 9c86890b437355bf9e8ff153dbf1a50a10fa5436 Mon Sep 17 00:00:00 2001 From: amrita Date: Thu, 21 Apr 2022 15:18:23 +0545 Subject: [PATCH 1/2] Improve Then step in apiShareReshareToShares3 suite --- .../reShareUpdate.feature | 1 + .../reShareWithExpiryDate.feature | 178 ++++++++---------- ...eShareWithExpiryDateOc10Issue37013.feature | 17 +- 3 files changed, 85 insertions(+), 111 deletions(-) diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature index 06304bb00118..d417c8d14986 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature @@ -145,6 +145,7 @@ Feature: sharing | permissions | create,update,read | When user "Brian" deletes the last share using the sharing API Then the OCS status code should be "" + And the HTTP status code should be "200" And user "Carol" should not have any received shares Examples: | ocs_api_version | ocs_status_code | diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature index be2d035d6b14..033dd31bf7e3 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature @@ -24,9 +24,7 @@ Feature: resharing a resource with an expiration date | expireDate | +3 days | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | +3 days | And the response when user "Carol" gets the info of the last share should include @@ -52,9 +50,7 @@ Feature: resharing a resource with an expiration date | expireDate | +3 days | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | +3 days | And the response when user "Carol" gets the info of the last share should include @@ -68,7 +64,7 @@ Feature: resharing a resource with an expiration date Scenario Outline: resharing with user using the sharing API with expire days set and combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30" And user "Carol" has been created with default attributes and without skeleton files And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share" @@ -80,25 +76,23 @@ Feature: resharing a resource with an expiration date | shareWith | Carol | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | | And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | expected-expire-date | ocs_status_code | - | 1 | yes | yes | +30 days | 100 | - | 2 | yes | yes | +30 days | 200 | - | 1 | no | yes | | 100 | - | 2 | no | yes | | 200 | + | ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code | + | 1 | yes | +30 days | 100 | + | 2 | yes | +30 days | 200 | + | 1 | no | | 100 | + | 2 | no | | 200 | @skipOnOcV10.3 @issue-ocis-reva-194 Scenario Outline: resharing with group using the sharing API with expire days set and combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_group_share" of app "core" has been set to "30" And user "Carol" has been created with default attributes and without skeleton files And group "grp1" has been created @@ -112,25 +106,23 @@ Feature: resharing a resource with an expiration date | shareWith | grp1 | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | | And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | expected-expire-date | ocs_status_code | - | 1 | yes | yes | +30 days | 100 | - | 2 | yes | yes | +30 days | 200 | - | 1 | no | yes | | 100 | - | 2 | no | yes | | 200 | + | ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code | + | 1 | yes | +30 days | 100 | + | 2 | yes | +30 days | 200 | + | 1 | no | | 100 | + | 2 | no | | 200 | @skipOnOcV10.3 Scenario Outline: resharing with user using the sharing API without expire days set and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And user "Carol" has been created with default attributes and without skeleton files And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share" And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice" @@ -141,25 +133,23 @@ Feature: resharing a resource with an expiration date | shareWith | Carol | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | | And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | expected-expire-date | ocs_status_code | - | 1 | yes | yes | +7 days | 100 | - | 2 | yes | yes | +7 days | 200 | - | 1 | no | yes | | 100 | - | 2 | no | yes | | 200 | + | ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code | + | 1 | yes | +7 days | 100 | + | 2 | yes | +7 days | 200 | + | 1 | no | | 100 | + | 2 | no | | 200 | @skipOnOcV10.3 @issue-ocis-reva-194 Scenario Outline: resharing with group using the sharing API without expire days set and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "yes" And user "Carol" has been created with default attributes and without skeleton files And group "grp1" has been created And user "Carol" has been added to group "grp1" @@ -172,25 +162,23 @@ Feature: resharing a resource with an expiration date | shareWith | grp1 | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | | And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | expected-expire-date | ocs_status_code | - | 1 | yes | yes | +7 days | 100 | - | 2 | yes | yes | +7 days | 200 | - | 1 | no | yes | | 100 | - | 2 | no | yes | | 200 | + | ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code | + | 1 | yes | +7 days | 100 | + | 2 | yes | +7 days | 200 | + | 1 | no | | 100 | + | 2 | no | | 200 | @skipOnOcV10.3 Scenario Outline: resharing with user using the sharing API with expire days set and with combinations of default/enforce expire date enabled and specify expire date in share Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30" And user "Carol" has been created with default attributes and without skeleton files And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share" @@ -203,25 +191,23 @@ Feature: resharing a resource with an expiration date | expireDate | +20 days | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | +20 days | And the response when user "Carol" gets the info of the last share should include | expiration | +20 days | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | ocs_status_code | - | 1 | yes | yes | 100 | - | 2 | yes | yes | 200 | - | 1 | no | yes | 100 | - | 2 | no | yes | 200 | + | ocs_api_version | default-expire-date | ocs_status_code | + | 1 | yes | 100 | + | 2 | yes | 200 | + | 1 | no | 100 | + | 2 | no | 200 | @skipOnOcV10.3 @issue-ocis-reva-194 Scenario Outline: resharing with group using the sharing API with expire days set and with combinations of default/enforce expire date enabled and specify expire date in share Given using OCS API version "" And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_group_share" of app "core" has been set to "30" And user "Carol" has been created with default attributes and without skeleton files And group "grp1" has been created @@ -236,19 +222,17 @@ Feature: resharing a resource with an expiration date | expireDate | +20 days | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | +20 days | And the response when user "Carol" gets the info of the last share should include | expiration | +20 days | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | ocs_status_code | - | 1 | yes | yes | 100 | - | 2 | yes | yes | 200 | - | 1 | no | yes | 100 | - | 2 | no | yes | 200 | + | ocs_api_version | default-expire-date | ocs_status_code | + | 1 | yes | 100 | + | 2 | yes | 200 | + | 1 | no | 100 | + | 2 | no | 200 | @skipOnOcV10.3 Scenario Outline: Setting default expiry date and enforcement after the share is created @@ -259,7 +243,7 @@ Feature: resharing a resource with an expiration date And user "Brian" has shared file "/Shares/textfile0.txt" with user "Carol" And user "Carol" has accepted share "/textfile0.txt" offered by user "Brian" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "4" When user "Brian" gets the info of the last share using the sharing API Then the HTTP status code should be "200" @@ -269,17 +253,17 @@ Feature: resharing a resource with an expiration date And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | ocs_status_code | - | 1 | yes | yes | 100 | - | 2 | yes | yes | 200 | - | 1 | no | yes | 100 | - | 2 | no | yes | 200 | + | ocs_api_version | default-expire-date | ocs_status_code | + | 1 | yes | 100 | + | 2 | yes | 200 | + | 1 | no | 100 | + | 2 | no | 200 | @skipOnOcV10.3 @issue-ocis-reva-194 Scenario Outline: resharing group share with user using the sharing API with default expire date set and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30" And group "grp1" has been created And user "Carol" has been created with default attributes and without skeleton files @@ -293,25 +277,23 @@ Feature: resharing a resource with an expiration date | shareWith | Carol | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | | And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | expected-expire-date | ocs_status_code | - | 1 | yes | yes | +30 days | 100 | - | 2 | yes | yes | +30 days | 200 | - | 1 | no | yes | | 100 | - | 2 | no | yes | | 200 | + | ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code | + | 1 | yes | +30 days | 100 | + | 2 | yes | +30 days | 200 | + | 1 | no | | 100 | + | 2 | no | | 200 | @skipOnOcV10.3 @issue-ocis-reva-194 Scenario Outline: resharing group share with user using the sharing API with default expire date set and specifying expiration on share and with combinations of default/enforce expire date enabled Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30" And group "grp1" has been created And user "Carol" has been created with default attributes and without skeleton files @@ -326,25 +308,23 @@ Feature: resharing a resource with an expiration date | expireDate | +20 days | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | | And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | expected-expire-date | ocs_status_code | - | 1 | yes | yes | +20 days | 100 | - | 2 | yes | yes | +20 days | 200 | - | 1 | no | yes | +20 days | 100 | - | 2 | no | yes | +20 days | 200 | + | ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code | + | 1 | yes | +20 days | 100 | + | 2 | yes | +20 days | 200 | + | 1 | no | +20 days | 100 | + | 2 | no | +20 days | 200 | @skipOnOcV10.3 Scenario Outline: resharing using the sharing API with default expire date set but not enforced Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" - And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "no" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30" And user "Carol" has been created with default attributes and without skeleton files And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share" @@ -356,19 +336,17 @@ Feature: resharing a resource with an expiration date | shareWith | Carol | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include | expiration | | And the response when user "Carol" gets the info of the last share should include | expiration | | Examples: - | ocs_api_version | default-expire-date | enforce-expire-date | ocs_status_code | - | 1 | yes | no | 100 | - | 2 | yes | no | 200 | - | 1 | no | no | 100 | - | 2 | no | no | 200 | + | ocs_api_version | default-expire-date | ocs_status_code | + | 1 | yes | 100 | + | 2 | yes | 200 | + | 1 | no | 100 | + | 2 | no | 200 | @skipOnOcV10 @skipOnOcV10.3 @issue-37013 Scenario Outline: reshare extends the received expiry date up to the default by default @@ -391,9 +369,7 @@ Feature: resharing a resource with an expiration date | shareWith | Carol | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Alice" should include | expiration | +20 days | And the response when user "Carol" gets the info of the last share should include @@ -408,7 +384,7 @@ Feature: resharing a resource with an expiration date | 2 | no | no | 200 | @skipOnOcV10 @skipOnOcV10.3 @issue-37013 - Scenario Outline: reshare can extend the received expiry date further into the future + Scenario Outline: reshare cannot extend the received expiry date further into the future Given using OCS API version "" And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "no" @@ -442,7 +418,7 @@ Feature: resharing a resource with an expiration date @skipOnOcV10 @skipOnOcV10.3 @issue-37013 Scenario Outline: reshare cannot extend the received expiry date past the default when the default is enforced Given using OCS API version "" - And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30" And user "Carol" has been created with default attributes and without skeleton files @@ -464,6 +440,6 @@ Feature: resharing a resource with an expiration date And the information of the last share of user "Alice" should include | expiration | +20 days | Examples: - | ocs_api_version | default-expire-date | - | 1 | yes | - | 2 | yes | + | ocs_api_version | + | 1 | + | 2 | diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature index 64a96db7b742..bc3419a2a47c 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDateOc10Issue37013.feature @@ -31,9 +31,7 @@ Feature: resharing a resource with an expiration date | shareWith | Carol | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Alice" should include | expiration | +20 days | And the response when user "Carol" gets the info of the last share should include @@ -69,9 +67,7 @@ Feature: resharing a resource with an expiration date | expireDate | +40 days | Then the HTTP status code should be "200" And the OCS status code should be "" - When user "Carol" accepts share "/textfile0.txt" offered by user "Brian" using the sharing API - Then the HTTP status code should be "200" - And the OCS status code should be "" + And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Alice" should include | expiration | +20 days | And the response when user "Carol" gets the info of the last share should include @@ -86,7 +82,7 @@ Feature: resharing a resource with an expiration date @skipOnOcV10.3 @issue-37013 Scenario Outline: reshare cannot extend the received expiry date past the default when the default is enforced Given using OCS API version "" - And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "" + And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes" And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30" And user "Carol" has been created with default attributes and without skeleton files @@ -105,9 +101,10 @@ Feature: resharing a resource with an expiration date | expireDate | +40 days | Then the HTTP status code should be "" And the OCS status code should be "404" + And the sharing API should report to user "Carol" that no shares are in the pending state And the information of the last share of user "Alice" should include | expiration | +20 days | Examples: - | ocs_api_version | default-expire-date | http_status_code | - | 1 | yes | 200 | - | 2 | yes | 404 | + | ocs_api_version | http_status_code | + | 1 | 200 | + | 2 | 404 | From 6459cc2450613954754512e183cd2bb57172d770 Mon Sep 17 00:00:00 2001 From: Parajuli Kiran Date: Fri, 22 Apr 2022 10:39:10 +0545 Subject: [PATCH 2/2] Removed column with exact same values Signed-off-by: Parajuli Kiran --- .../reShareWithExpiryDate.feature | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature index 033dd31bf7e3..fe4d2d2c487a 100644 --- a/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature +++ b/tests/acceptance/features/apiShareReshareToShares3/reShareWithExpiryDate.feature @@ -310,15 +310,15 @@ Feature: resharing a resource with an expiration date And the OCS status code should be "" And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian" And the information of the last share of user "Brian" should include - | expiration | | + | expiration | +20 days | And the response when user "Carol" gets the info of the last share should include - | expiration | | + | expiration | +20 days | Examples: - | ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code | - | 1 | yes | +20 days | 100 | - | 2 | yes | +20 days | 200 | - | 1 | no | +20 days | 100 | - | 2 | no | +20 days | 200 | + | ocs_api_version | default-expire-date | ocs_status_code | + | 1 | yes | 100 | + | 2 | yes | 200 | + | 1 | no | 100 | + | 2 | no | 200 | @skipOnOcV10.3 Scenario Outline: resharing using the sharing API with default expire date set but not enforced