From 6459cc2450613954754512e183cd2bb57172d770 Mon Sep 17 00:00:00 2001 From: Parajuli Kiran Date: Fri, 22 Apr 2022 10:39:10 +0545 Subject: [PATCH] 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