Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[stable10] API acceptance tests to unlock files/folders #34331

Merged
merged 1 commit into from
Jan 30, 2019
Merged

[stable10] API acceptance tests to unlock files/folders #34331

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
324 changes: 324 additions & 0 deletions tests/acceptance/features/apiWebdavLocks/unlock.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,324 @@
@api
Feature: UNLOCK locked items

Background:
Given user "user0" has been created with default attributes

Scenario Outline: unlock a single lock set by the user itself
Given using <dav-path> DAV path
And user "user0" has locked folder "PARENT" setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks the last created lock of folder "PARENT" using the WebDAV API
Then 0 locks should be reported for folder "PARENT" of user "user0" by the WebDAV API
And 0 locks should be reported for folder "PARENT/CHILD" of user "user0" by the WebDAV API
And 0 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: unlock one of multiple locks set by the user itself
Given using <dav-path> DAV path
And user "user0" has locked file "textfile0.txt" setting following properties
| lockscope | shared |
And user "user0" has locked file "textfile0.txt" setting following properties
| lockscope | shared |
When user "user0" unlocks the last created lock of file "textfile0.txt" using the WebDAV API
Then 1 locks should be reported for file "textfile0.txt" of user "user0" by the WebDAV API
Examples:
| dav-path |
| old |
| new |

Scenario Outline: unlocking a file that was locked by the user locking the folder above is not possible
Given using <dav-path> DAV path
And user "user0" has locked folder "PARENT/CHILD" setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks file "PARENT/CHILD/child.txt" with the last created lock of folder "PARENT/CHILD" using the WebDAV API
Then 1 locks should be reported for file "PARENT/CHILD/child.txt" of user "user0" by the WebDAV API
And 2 locks should be reported for folder "PARENT/CHILD" of user "user0" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as share receiver unlocking a shared file locked by the file owner is not possible. To unlock use the owners locktoken
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has locked file "PARENT/parent.txt" setting following properties
| lockscope | <lock-scope> |
And user "user0" has shared file "PARENT/parent.txt" with user "user1"
When user "user1" unlocks file "parent.txt" with the last created lock of file "PARENT/parent.txt" of user "user0" using the WebDAV API
Then the HTTP status code should be "403"
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 1 locks should be reported for file "parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as share receiver unlocking a file in a share locked by the file owner is not possible. To unlock use the owners locktoken
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has locked file "PARENT/parent.txt" setting following properties
| lockscope | <lock-scope> |
And user "user0" has shared folder "PARENT" with user "user1"
When user "user1" unlocks file "PARENT (2)/parent.txt" with the last created lock of file "PARENT/parent.txt" of user "user0" using the WebDAV API
Then the HTTP status code should be "403"
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 1 locks should be reported for file "PARENT (2)/parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as share receiver unlocking a shared folder locked by the file owner is not possible. To unlock use the owners locktoken
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has locked folder "PARENT" setting following properties
| lockscope | <lock-scope> |
And user "user0" has shared folder "PARENT" with user "user1"
When user "user1" unlocks folder "PARENT (2)" with the last created lock of folder "PARENT" of user "user0" using the WebDAV API
Then the HTTP status code should be "403"
And 3 locks should be reported for folder "PARENT" of user "user0" by the WebDAV API
And 2 locks should be reported for folder "PARENT/CHILD" of user "user0" by the WebDAV API
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 3 locks should be reported for folder "PARENT (2)" of user "user1" by the WebDAV API
And 2 locks should be reported for folder "PARENT (2)/CHILD" of user "user1" by the WebDAV API
And 1 locks should be reported for file "PARENT (2)/parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as share receiver unlocking a shared file locked by the file owner is not possible. To unlock use the owners locktoken
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has locked file "PARENT/parent.txt" setting following properties
| lockscope | <lock-scope> |
And user "user0" has shared file "PARENT/parent.txt" with user "user1"
When user "user1" unlocks file "parent.txt" with the last created lock of file "PARENT/parent.txt" of user "user0" using the WebDAV API
Then the HTTP status code should be "403"
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 1 locks should be reported for file "parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as share receiver unlock a shared file
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has shared file "PARENT/parent.txt" with user "user1"
And user "user1" has locked file "parent.txt" setting following properties
| lockscope | <lock-scope> |
When user "user1" unlocks the last created lock of file "parent.txt" using the WebDAV API
Then the HTTP status code should be "204"
And 0 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 0 locks should be reported for file "parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as owner unlocking a shared file locked by the receiver is not possible. To unlock use the receivers locktoken
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has shared file "PARENT/parent.txt" with user "user1"
And user "user1" has locked file "parent.txt" setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks file "PARENT/parent.txt" with the last created lock of file "parent.txt" of user "user1" using the WebDAV API
Then the HTTP status code should be "403"
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 1 locks should be reported for file "parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as owner unlocking a file in a share that was locked by the share receiver is not possible. To unlock use the receivers locktoken
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has shared folder "PARENT" with user "user1"
And user "user1" has locked file "PARENT (2)/parent.txt" setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks file "PARENT/parent.txt" with the last created lock of file "PARENT (2)/parent.txt" of user "user1" using the WebDAV API
Then the HTTP status code should be "403"
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 1 locks should be reported for file "PARENT (2)/parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as owner unlocking a shared folder locked by the share receiver is not possible. To unlock use the receivers locktoken
Given using <dav-path> DAV path
And user "user1" has been created with default attributes
And user "user0" has shared folder "PARENT" with user "user1"
And user "user1" has locked folder "PARENT (2)" setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks folder "PARENT" with the last created lock of folder "PARENT (2)" of user "user1" using the WebDAV API
Then the HTTP status code should be "403"
And 3 locks should be reported for folder "PARENT" of user "user0" by the WebDAV API
And 2 locks should be reported for folder "PARENT/CHILD" of user "user0" by the WebDAV API
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
And 3 locks should be reported for folder "PARENT (2)" of user "user1" by the WebDAV API
And 2 locks should be reported for folder "PARENT (2)/CHILD" of user "user1" by the WebDAV API
And 1 locks should be reported for file "PARENT (2)/parent.txt" of user "user1" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

@issue-34302
Scenario Outline: as public unlocking a file in a share that was locked by the file owner is not possible. To unlock use the owners locktoken
Given user "user0" has created a public link share of folder "PARENT" with change permission
And user "user0" has locked file "PARENT/parent.txt" setting following properties
| lockscope | <lock-scope> |
When the public unlocks file "/parent.txt" with the last created lock of file "PARENT/parent.txt" of user "user0" using the WebDAV API
Then the HTTP status code should be "409"
#Then the HTTP status code should be "403"
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| lock-scope |
| shared |
| exclusive |

@issue-34302
Scenario Outline: as public unlocking a shared folder locked by the file owner is not possible. To unlock use the owners locktoken
Given user "user0" has created a public link share of folder "PARENT" with change permission
And user "user0" has locked folder "PARENT" setting following properties
| lockscope | <lock-scope> |
When the public unlocks folder "/PARENT" with the last created lock of file "PARENT" of user "user0" using the WebDAV API
Then the HTTP status code should be "409"
#Then the HTTP status code should be "403"
And 3 locks should be reported for folder "PARENT" of user "user0" by the WebDAV API
And 2 locks should be reported for folder "PARENT/CHILD" of user "user0" by the WebDAV API
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| lock-scope |
| shared |
| exclusive |

@issue-34302
Scenario Outline: as public unlocking a shared file locked by the file owner is not possible. To unlock use the owners locktoken
Given user "user0" has created a public link share of file "PARENT/parent.txt" with change permission
And user "user0" has locked file "PARENT/parent.txt" setting following properties
| lockscope | <lock-scope> |
When the public unlocks folder "/" with the last created lock of file "PARENT/parent.txt" of user "user0" using the WebDAV API
Then the HTTP status code should be "409"
#Then the HTTP status code should be "403"
And 1 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| lock-scope |
| shared |
| exclusive |

Scenario Outline: as owner unlock a publicly shared file that was locked by the public
Given using <dav-path> DAV path
And user "user0" has created a public link share of file "PARENT/parent.txt" with change permission
And the public has locked the last public shared file setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks file "PARENT/parent.txt" with the last created public lock of file "/" using the WebDAV API
Then the HTTP status code should be "204"
And 0 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as owner unlock a file in a public folder that was locked by the public
Given using <dav-path> DAV path
And user "user0" has created a public link share of folder "PARENT" with change permission
And the public has locked "parent.txt" in the last public shared folder setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks file "PARENT/parent.txt" with the last created public lock of file "parent.txt" using the WebDAV API
Then the HTTP status code should be "204"
And 0 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

Scenario Outline: as owner unlock a folder in a public folder that was locked by the public
Given using <dav-path> DAV path
And user "user0" has created a public link share of folder "PARENT" with change permission
And the public has locked "CHILD" in the last public shared folder setting following properties
| lockscope | <lock-scope> |
When user "user0" unlocks folder "PARENT/CHILD" with the last created public lock of file "CHILD" using the WebDAV API
Then the HTTP status code should be "204"
And 0 locks should be reported for folder "PARENT/CHILD" of user "user0" by the WebDAV API
And 0 locks should be reported for file "PARENT/CHILD/child.txt" of user "user0" by the WebDAV API
Examples:
| dav-path | lock-scope |
| old | shared |
| old | exclusive |
| new | shared |
| new | exclusive |

@issue-34302
Scenario Outline: as public unlock a publicly shared file that was locked by the public
Given user "user0" has created a public link share of file "PARENT/parent.txt" with change permission
And the public has locked the last public shared file setting following properties
| lockscope | <lock-scope> |
When the public unlocks file "/" using the WebDAV API
Then the HTTP status code should be "409"
#Then the HTTP status code should be "204"
#And 0 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| lock-scope |
| shared |
| exclusive |

@issue-34302
Scenario Outline: as public unlock a file in a public folder that was locked by the public
Given user "user0" has created a public link share of folder "PARENT" with change permission
And the public has locked "parent.txt" in the last public shared folder setting following properties
| lockscope | <lock-scope> |
When the public unlocks file "parent.txt" using the WebDAV API
Then the HTTP status code should be "409"
#Then the HTTP status code should be "204"
#And 0 locks should be reported for file "PARENT/parent.txt" of user "user0" by the WebDAV API
Examples:
| lock-scope |
| shared |
| exclusive |

@issue-34302
Scenario Outline: as public unlock a subfolder of a public folder that was locked by the public
Given user "user0" has created a public link share of folder "PARENT" with change permission
And the public has locked "CHILD" in the last public shared folder setting following properties
| lockscope | <lock-scope> |
When the public unlocks folder "CHILD" using the WebDAV API
Then the HTTP status code should be "409"
#Then the HTTP status code should be "204"
#And 0 locks should be reported for file "PARENT/CHILD/child.txt" of user "user0" by the WebDAV API
#And 0 locks should be reported for file "PARENT/CHILD" of user "user0" by the WebDAV API
Examples:
| lock-scope |
| shared |
| exclusive |
Loading