-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tests-Only] Refactor apiShareCreateSpecial1 to use Shares folder #37938
Conversation
ae73e1a
to
d583627
Compare
Codecov Report
@@ Coverage Diff @@
## master #37938 +/- ##
============================================
- Coverage 64.71% 64.13% -0.59%
Complexity 19442 19442
============================================
Files 1286 1285 -1
Lines 76019 75978 -41
Branches 1336 1336
============================================
- Hits 49196 48727 -469
- Misses 26429 26857 +428
Partials 394 394
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
6393abe
to
bf3cf0d
Compare
.../acceptance/features/apiShareCreateSpecialShares1/createShareWhenExcludedFromSharing.feature
Show resolved
Hide resolved
.../acceptance/features/apiShareCreateSpecialShares1/createShareWhenExcludedFromSharing.feature
Show resolved
Hide resolved
.../acceptance/features/apiShareCreateSpecialShares1/createShareWhenExcludedFromSharing.feature
Show resolved
Hide resolved
.../acceptance/features/apiShareCreateSpecialShares1/createShareWhenExcludedFromSharing.feature
Show resolved
Hide resolved
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Outdated
Show resolved
Hide resolved
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Outdated
Show resolved
Hide resolved
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Show resolved
Hide resolved
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Show resolved
Hide resolved
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Show resolved
Hide resolved
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Show resolved
Hide resolved
I also raised issue #37944 - it applies to a lot of these "sharing to share_folder" scenarios in multiple PRs. So we can sort that out next week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some scenarios have
Then the status code should be <code>
step which checks the status of accepting the share not creating the share.
I have not commented on all of them. Please go through all the scenarios fix those to check the status of Sharing step.
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Show resolved
Hide resolved
Then the OCS status code should be "<ocs_status_code>" | ||
And the HTTP status code should be "<http_status_code>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.
tests/acceptance/features/apiShareCreateSpecialShares1/createShareExpirationDate.feature
Show resolved
Hide resolved
Then the OCS status code should be "<ocs_status_code>" | ||
And the HTTP status code should be "<http_status_code>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.
Then the OCS status code should be "<ocs_status_code>" | ||
And the HTTP status code should be "200" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.
Then the OCS status code should be "<ocs_status_code>" | ||
And the HTTP status code should be "200" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This step is supposed to check the status code of sharing step but here it checks the status of accepting the share.
…de check in features
bf3cf0d
to
ab80ea6
Compare
Description
This PR makes
apiShareCreateSpecial1
test scenarios to be valid in both oC10 and OCIS. OCIS always puts received shares into a folder called Shares for the share receiver. On OCIS, auto-accept shares is always disabled.Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: