Refactor feature files to add correct description
This commit is contained in:
+4
-1
@@ -1,12 +1,15 @@
|
||||
@api @files_sharing-app-required @issue-1327
|
||||
Feature: shares are received in the default folder for received shares
|
||||
As a user
|
||||
I want to share the default Shares folder
|
||||
So that I can make sure it does not work
|
||||
|
||||
Background:
|
||||
Given auto-accept shares has been disabled
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
|
||||
Scenario Outline: Do not allow sharing of the entire share_folder
|
||||
Scenario Outline: do not allow sharing of the entire share folder
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
|
||||
+3
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: sharing works when a username and group name are the same
|
||||
As a user
|
||||
I want to share resources with group and users having same name
|
||||
So that I can make sure that the sharing works
|
||||
|
||||
Background:
|
||||
Given auto-accept shares has been disabled
|
||||
|
||||
+16
-13
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: share resources where the sharee receives the share in multiple ways
|
||||
As a user
|
||||
I want to receives the same resource share from multiple channels
|
||||
So that I can make sure that the sharing works
|
||||
|
||||
Background:
|
||||
Given auto-accept shares has been disabled
|
||||
@@ -38,7 +41,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| 2 | 200 | /textfile0 (2).txt |
|
||||
|
||||
@issue-1289
|
||||
Scenario Outline: Share of folder and sub-folder to same user
|
||||
Scenario Outline: share of folder and sub-folder to same user
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And group "grp4" has been created
|
||||
And user "Brian" has been added to group "grp4"
|
||||
@@ -191,7 +194,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| 2 | 200 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to user with all permissions and its child folder to group with read permission then check create operation
|
||||
Scenario Outline: sharing parent folder to user with all permissions and its child folder to group with read permission then check create operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -225,7 +228,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to user with all permissions and its child folder to group with read permission then check rename operation
|
||||
Scenario Outline: sharing parent folder to user with all permissions and its child folder to group with read permission then check rename operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -260,7 +263,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to user with all permissions and its child folder to group with read permission then check delete operation
|
||||
Scenario Outline: sharing parent folder to user with all permissions and its child folder to group with read permission then check delete operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -295,7 +298,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to user with all permissions and its child folder to group with read permission then check reshare operation
|
||||
Scenario Outline: sharing parent folder to user with all permissions and its child folder to group with read permission then check reshare operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -334,7 +337,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to group with read permission and its child folder to user with all permissions then check create operation
|
||||
Scenario Outline: sharing parent folder to group with read permission and its child folder to user with all permissions then check create operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -369,7 +372,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to group with read permission and its child folder to user with all permissions then check rename operation
|
||||
Scenario Outline: sharing parent folder to group with read permission and its child folder to user with all permissions then check rename operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -404,7 +407,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to group with read permission and its child folder to user with all permissions then check delete operation
|
||||
Scenario Outline: sharing parent folder to group with read permission and its child folder to user with all permissions then check delete operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -439,7 +442,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to group with read permission and its child folder to user with all permissions then check reshare operation
|
||||
Scenario Outline: sharing parent folder to group with read permission and its child folder to user with all permissions then check reshare operation
|
||||
Given group "grp1" has been created
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
And user "Carol" has created the following folders
|
||||
@@ -474,7 +477,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Sharing parent folder to one group with all permissions and its child folder to another group with read permission
|
||||
Scenario Outline: sharing parent folder to one group with all permissions and its child folder to another group with read permission
|
||||
Given these groups have been created:
|
||||
| groupname |
|
||||
| grp1 |
|
||||
@@ -519,7 +522,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| /child1 |
|
||||
|
||||
|
||||
Scenario Outline: Share receiver renames the received group share and shares same folder through user share again
|
||||
Scenario Outline: share receiver renames the received group share and shares same folder through user share again
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And group "grp" has been created
|
||||
And user "Brian" has been added to group "grp"
|
||||
@@ -550,7 +553,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| 2 | 200 |
|
||||
|
||||
|
||||
Scenario Outline: Share receiver renames a group share and receives same resource through user share with additional permissions
|
||||
Scenario Outline: share receiver renames a group share and receives same resource through user share with additional permissions
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And group "grp" has been created
|
||||
And user "Brian" has been added to group "grp"
|
||||
@@ -579,7 +582,7 @@ Feature: share resources where the sharee receives the share in multiple ways
|
||||
| 2 |
|
||||
|
||||
|
||||
Scenario Outline: Share receiver renames a group share and receives same resource through user share with less permissions
|
||||
Scenario Outline: share receiver renames a group share and receives same resource through user share with less permissions
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And group "grp" has been created
|
||||
And user "Brian" has been added to group "grp"
|
||||
|
||||
+5
-2
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required @issue-1328
|
||||
Feature: share resources with a disabled user
|
||||
As a user
|
||||
I want to share resources to disabled user
|
||||
So that I can make sure it doesn't work
|
||||
|
||||
Background:
|
||||
Given auto-accept shares has been disabled
|
||||
@@ -7,7 +10,7 @@ Feature: share resources with a disabled user
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
|
||||
|
||||
@issue-2212
|
||||
Scenario Outline: Creating a new share with a disabled user
|
||||
Scenario Outline: creating a new share with a disabled user
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has been disabled
|
||||
@@ -19,7 +22,7 @@ Feature: share resources with a disabled user
|
||||
| 1 | 997 |
|
||||
|
||||
|
||||
Scenario: Creating a new share with a disabled user
|
||||
Scenario: creating a new share with a disabled user
|
||||
Given using OCS API version "2"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has been disabled
|
||||
|
||||
+8
-5
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: cannot share resources with invalid permissions
|
||||
As a user
|
||||
I want to share resources with invalid permission
|
||||
So that I can make sure it doesn't work
|
||||
|
||||
Background:
|
||||
Given auto-accept shares has been disabled
|
||||
@@ -8,7 +11,7 @@ Feature: cannot share resources with invalid permissions
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
|
||||
|
||||
Scenario Outline: Cannot create a share of a file or folder with invalid permissions
|
||||
Scenario Outline: cannot create a share of a file or folder with invalid permissions
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
When user "Alice" creates a share using the sharing API with settings
|
||||
@@ -33,7 +36,7 @@ Feature: cannot share resources with invalid permissions
|
||||
| 2 | 404 | 404 | PARENT | 32 |
|
||||
|
||||
|
||||
Scenario Outline: Cannot create a share of a file with a user with only create permission
|
||||
Scenario Outline: cannot create a share of a file with a user with only create permission
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
When user "Alice" creates a share using the sharing API with settings
|
||||
@@ -52,7 +55,7 @@ Feature: cannot share resources with invalid permissions
|
||||
| 2 | 400 |
|
||||
|
||||
|
||||
Scenario Outline: Cannot create a share of a file with a user with only (create,delete) permission
|
||||
Scenario Outline: cannot create a share of a file with a user with only (create,delete) permission
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
When user "Alice" creates a share using the sharing API with settings
|
||||
@@ -73,7 +76,7 @@ Feature: cannot share resources with invalid permissions
|
||||
| 2 | 400 | create,delete |
|
||||
|
||||
|
||||
Scenario Outline: Cannot create a share of a file with a group with only create permission
|
||||
Scenario Outline: cannot create a share of a file with a group with only create permission
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And group "grp1" has been created
|
||||
@@ -94,7 +97,7 @@ Feature: cannot share resources with invalid permissions
|
||||
| 2 | 400 |
|
||||
|
||||
|
||||
Scenario Outline: Cannot create a share of a file with a group with only (create,delete) permission
|
||||
Scenario Outline: cannot create a share of a file with a group with only (create,delete) permission
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And group "grp1" has been created
|
||||
|
||||
Reference in New Issue
Block a user