[tests-only] [full-ci] Test with core branch reva-issue-2916

[phil-davis]

Related issue #2916

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[phil-davis]

https://drone.cernbox.cern.ch/cs3org/reva/7391/15/6

  Scenario: After losing share permissions user can still delete a previously reshared share                      # /drone/src/tmp/testrunner/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature:137
    Given using OCS API version "1"                                                                               # FeatureContext::usingOcsApiVersion()
    And user "Alice" has created folder "/TMP"                                                                    # FeatureContext::userHasCreatedFolder()
    And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"       # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    And user "Brian" has accepted share "/TMP" offered by user "Alice"                                            # FeatureContext::userHasReactedToShareOfferedBy()
    And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,create,update,read" # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    And user "Carol" has accepted share "/TMP" offered by user "Brian"                                            # FeatureContext::userHasReactedToShareOfferedBy()
    And user "Alice" has updated the last share of "Alice" with                                                   # FeatureContext::userHasUpdatedTheLastShareOfWith()
      | permissions | create,update,read |
    When user "Brian" deletes the last share using the sharing API                                                # FeatureContext::userDeletesLastShareUsingTheSharingApi()
    Then the OCS status code should be "100"                                                                      # OCSContext::theOCSStatusCodeShouldBe()
      OCS status code is not any of the expected values 100 got 996
      Failed asserting that an array contains '996'.

  Scenario: After losing share permissions user can still delete a previously reshared share                      # /drone/src/tmp/testrunner/tests/acceptance/features/apiShareReshareToShares3/reShareUpdate.feature:152
    Given using OCS API version "2"                                                                               # FeatureContext::usingOcsApiVersion()
    And user "Alice" has created folder "/TMP"                                                                    # FeatureContext::userHasCreatedFolder()
    And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"       # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    And user "Brian" has accepted share "/TMP" offered by user "Alice"                                            # FeatureContext::userHasReactedToShareOfferedBy()
    And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,create,update,read" # FeatureContext::userHasSharedFileWithUserUsingTheSharingApi()
    And user "Carol" has accepted share "/TMP" offered by user "Brian"                                            # FeatureContext::userHasReactedToShareOfferedBy()
    And user "Alice" has updated the last share of "Alice" with                                                   # FeatureContext::userHasUpdatedTheLastShareOfWith()
      | permissions | create,update,read |
    When user "Brian" deletes the last share using the sharing API                                                # FeatureContext::userDeletesLastShareUsingTheSharingApi()
    Then the OCS status code should be "200"                                                                      # OCSContext::theOCSStatusCodeShouldBe()
      OCS status code is not any of the expected values 200 got 996
      Failed asserting that an array contains '996'.