[full-ci] [tests-only] Removed tag personalSpace, and refactored the example tables (#6250)
* Refactored personalSpace tagged scenarios * Fixed line numbers in expected failure
This commit is contained in:
@@ -21,13 +21,13 @@ Feature: there can be only one exclusive lock on a resource
|
||||
| new | shared |
|
||||
| new | exclusive |
|
||||
|
||||
@personalSpace
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path | lock-scope |
|
||||
| spaces | shared |
|
||||
| spaces | exclusive |
|
||||
|
||||
|
||||
|
||||
Scenario Outline: a share receiver cannot lock a resource exclusively locked by itself
|
||||
Given using <dav-path> DAV path
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
@@ -48,13 +48,13 @@ Feature: there can be only one exclusive lock on a resource
|
||||
| new | shared |
|
||||
| new | exclusive |
|
||||
|
||||
@personalSpace
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path | lock-scope |
|
||||
| spaces | shared |
|
||||
| spaces | exclusive |
|
||||
|
||||
|
||||
|
||||
Scenario Outline: a share receiver cannot lock a resource exclusively locked by the owner
|
||||
Given using <dav-path> DAV path
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
@@ -75,13 +75,13 @@ Feature: there can be only one exclusive lock on a resource
|
||||
| new | shared |
|
||||
| new | exclusive |
|
||||
|
||||
@personalSpace
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path | lock-scope |
|
||||
| spaces | shared |
|
||||
| spaces | exclusive |
|
||||
|
||||
|
||||
|
||||
Scenario Outline: a share owner cannot lock a resource exclusively locked by a share receiver
|
||||
Given using <dav-path> DAV path
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
@@ -102,7 +102,7 @@ Feature: there can be only one exclusive lock on a resource
|
||||
| new | shared |
|
||||
| new | exclusive |
|
||||
|
||||
@personalSpace
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path | lock-scope |
|
||||
| spaces | shared |
|
||||
|
||||
@@ -4,7 +4,7 @@ Feature: actions on a locked item are possible if the token is sent with the req
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
|
||||
|
||||
Scenario Outline: two users having both a shared lock can use the resource
|
||||
Given using <dav-path> DAV path
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
@@ -29,7 +29,7 @@ Feature: actions on a locked item are possible if the token is sent with the req
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@personalSpace
|
||||
@skipOnRevaMaster
|
||||
Examples:
|
||||
| dav-path |
|
||||
| spaces |
|
||||
|
||||
Reference in New Issue
Block a user