-
Notifications
You must be signed in to change notification settings - Fork 186
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][full-ci] Add test for unlocking project space file #7698
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
Feature: unlock locked items | ||
As a user | ||
I want to unlock the resources previously locked by myself | ||
So that other users can make changes to the resources | ||
|
||
Background: | ||
Given user "Alice" has been created with default attributes and without skeleton files | ||
|
||
@issue-7696 | ||
Scenario Outline: unlock a locked file in project space | ||
Given using spaces DAV path | ||
And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API | ||
And user "Alice" has created a space "project-space" with the default quota using the Graph API | ||
And user "Alice" has uploaded a file inside space "project-space" with content "some data" to "textfile.txt" | ||
And user "Alice" has locked file "textfile.txt" inside space "project-space" setting the following properties | ||
| lockscope | <lock-scope> | | ||
When user "Alice" unlocks the last created lock of file "textfile.txt" inside space "project-space" using the WebDAV API | ||
Then the HTTP status code should be "204" | ||
Examples: | ||
| lock-scope | | ||
| shared | | ||
| exclusive | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
do we already have coverage for locking project space file?
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.
I try to search but could not find so I think there is no coverage for locking and unlocking project spaces
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.
Then I would suggest adding locking and unlocking tests
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.
there is some coverage for locking the project space file
ocis/tests/acceptance/features/apiLocks/lockFiles.feature
Line 91 in 841ab73
ocis/tests/acceptance/features/apiLocks/lockFiles.feature
Line 117 in 841ab73
ocis/tests/acceptance/features/apiLocks/lockFiles.feature
Line 144 in 841ab73
For the first batch of lock/unlock tests IMO we can shift the tests from core to ocis and provide the coverage for unlock as per there is coverage for locking and other edge cases can be added later or in other PR