sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add proper description to a feature file

Browse Source
This commit is contained in:
Swikriti Tripathi
2023-05-09 10:07:18 +05:45
parent 5b909f5923
commit c969faf8ef
20 changed files with 171 additions and 138 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature
+3
View File
@@ -1,5 +1,8 @@
@api
Feature: sharing
As a user
I want to share resources with other users
So that they can have access to the resources
Background:
Given these users have been created with default attributes and without skeleton files:
tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature
+6 -3
View File
@@ -1,5 +1,8 @@
@api @issue-1289 @issue-1328
Feature: sharing
As a user
I want to move shares that I received
So that I can organise them according to my needs
Background:
Given these users have been created with default attributes and without skeleton files:
@@ -24,7 +27,7 @@ Feature: sharing
| new |
Scenario Outline: Move files between shares by same user
Scenario Outline: move files between shares by same user
Given using <dav_version> DAV path
And user "Alice" has created folder "share1"
And user "Alice" has created folder "share2"
@@ -46,7 +49,7 @@ Feature: sharing
| new |
Scenario Outline: Move files between shares by same user added by sharee
Scenario Outline: move files between shares by same user added by sharee
Given using <dav_version> DAV path
And user "Alice" has created folder "share1"
And user "Alice" has created folder "share2"
@@ -68,7 +71,7 @@ Feature: sharing
| new |
Scenario Outline: Move files between shares by different users
Scenario Outline: move files between shares by different users
Given using <dav_version> DAV path
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature
+12 -9
View File
@@ -1,5 +1,8 @@
@api
Feature: sharing
As a user
I want to get all the shares
So that I can know I have proper access to them
Background:
Given these users have been created with default attributes and without skeleton files:
@@ -8,12 +11,12 @@ Feature: sharing
| Brian |
@smokeTest @issue-1258
Scenario Outline: getting all shares of a user using that user
Scenario Outline: getting all shares from a user
Given using OCS API version "<ocs_api_version>"
And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt"
And user "Alice" has shared file "file_to_share.txt" with user "Brian"
And user "Brian" has accepted share "/file_to_share.txt" offered by user "Alice"
When user "Alice" gets all shares shared by him using the sharing API
When user "Alice" gets all shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And file "/Shares/file_to_share.txt" should be included in the response
@@ -49,7 +52,7 @@ Feature: sharing
And user "Alice" has shared file "textfile0.txt" with user "Carol"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
And user "Carol" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Alice" gets all the shares from the file "textfile0.txt" using the sharing API
When user "Alice" gets all the shares of the file "textfile0.txt" using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And user "Brian" should be included in the response
@@ -72,7 +75,7 @@ Feature: sharing
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
And user "Brian" has shared file "/Shares/textfile0.txt" with user "Carol"
And user "Carol" has accepted share "/textfile0.txt" offered by user "Brian"
When user "Alice" gets all the shares with reshares from the file "textfile0.txt" using the sharing API
When user "Alice" gets all the shares with reshares of the file "textfile0.txt" using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And user "Brian" should be included in the response
@@ -84,7 +87,7 @@ Feature: sharing
| 2 | 200 |
@smokeTest
Scenario Outline: User's own shares reshared to him don't appear when getting "shared with me" shares
Scenario Outline: resource cannot be reshared to resource owner
Given using OCS API version "<ocs_api_version>"
And group "grp1" has been created
And user "Carol" has been created with default attributes and without skeleton files
@@ -95,7 +98,7 @@ Feature: sharing
And user "Brian" has accepted share "/shared" offered by user "Carol"
And user "Brian" has shared folder "/Shares/shared" with group "grp1"
# no need to accept this share as it is Carol's file
When user "Carol" gets all the shares shared with him using the sharing API
When user "Carol" gets all the shares shared with her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And the last share id should not be included in the response
@@ -136,7 +139,7 @@ Feature: sharing
| 2 | 200 |
@issue-1233
Scenario Outline: Get a share with a user that didn't receive the share
Scenario Outline: get a share with a user that didn't receive the share
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
@@ -149,8 +152,8 @@ Feature: sharing
| 1 | 200 |
| 2 | 404 |
@issue-1289 @skipOnGraph
Scenario: Share of folder to a group, remove user from that group
@issue-1289 @skipOnGraph
Scenario: share a folder to a group, and remove user from that group
Given using OCS API version "1"
And user "Carol" has been created with default attributes and without skeleton files
And group "group0" has been created
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature
+2 -2
View File
@@ -1,8 +1,8 @@
@api
Feature: get the pending shares filtered by type (user, group etc)
As a user
I want to be able to know the pending shares that I have received of a particular type (user, group etc)
So that I can reduce the amount of data that has to be transferred to be just the data that I need
I want to filter the pending shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes and without skeleton files:
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature
+2 -2
View File
@@ -1,8 +1,8 @@
@api
Feature: get the received shares filtered by type (user, group etc)
As a user
I want to be able to know the shares that I have received of a particular type (user, group etc)
So that I can reduce the amount of data that has to be transferred to be just the data that I need
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes and without skeleton files:
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature
+2 -2
View File
@@ -1,8 +1,8 @@
@api
Feature: get the received shares filtered by type (user, group etc)
As a user
I want to be able to know the shares that I have received of a particular type (user, group etc)
So that I can reduce the amount of data that has to be transferred to be just the data that I need
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes and without skeleton files:
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature
+6 -6
View File
@@ -1,8 +1,8 @@
@api
Feature: get shares filtered by type (user, group etc)
As a user
I want to be able to know the shares that I have made of a particular type (user, group etc)
So that I can reduce the amount of data that has to be transferred to be just the data that I need
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes and without skeleton files:
@@ -35,7 +35,7 @@ Feature: get shares filtered by type (user, group etc)
Scenario Outline: getting shares shared to users
Given using OCS API version "<ocs_api_version>"
When user "Alice" gets the user shares shared by him using the sharing API
When user "Alice" gets the user shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And exactly 2 files or folders should be included in the response
@@ -49,7 +49,7 @@ Feature: get shares filtered by type (user, group etc)
Scenario Outline: getting shares shared to groups
Given using OCS API version "<ocs_api_version>"
When user "Alice" gets the group shares shared by him using the sharing API
When user "Alice" gets the group shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And exactly 2 files or folders should be included in the response
@@ -63,7 +63,7 @@ Feature: get shares filtered by type (user, group etc)
Scenario Outline: getting shares shared to public links
Given using OCS API version "<ocs_api_version>"
When user "Alice" gets the public link shares shared by him using the sharing API
When user "Alice" gets the public link shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And exactly 2 files or folders should be included in the response
@@ -77,7 +77,7 @@ Feature: get shares filtered by type (user, group etc)
Scenario Outline: getting shares shared to users and groups
Given using OCS API version "<ocs_api_version>"
When user "Alice" gets the user and group shares shared by him using the sharing API
When user "Alice" gets the user and group shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And exactly 4 files or folders should be included in the response
tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature
+5 -5
View File
@@ -1,8 +1,8 @@
@api
Feature: get shares filtered by type (user, group etc)
As a user
I want to be able to know the shares that I have made of a particular type (user, group etc)
So that I can reduce the amount of data that has to be transferred to be just the data that I need
I want to filter the shares that I have received of a particular type (user, group etc)
So that I can know about the status of the shares I've received
Background:
Given these users have been created with default attributes and without skeleton files:
@@ -31,7 +31,7 @@ Feature: get shares filtered by type (user, group etc)
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
When user "Alice" gets the user shares shared by him using the sharing API
When user "Alice" gets the user shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And no files or folders should be included in the response
@@ -53,7 +53,7 @@ Feature: get shares filtered by type (user, group etc)
And user "Alice" has created a public link share with settings
| path | /fileToShareWithPublic.txt |
| permissions | read |
When user "Alice" gets the group shares shared by him using the sharing API
When user "Alice" gets the group shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And no files or folders should be included in the response
@@ -73,7 +73,7 @@ Feature: get shares filtered by type (user, group etc)
And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
When user "Alice" gets the public link shares shared by him using the sharing API
When user "Alice" gets the public link shares shared by her using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And no files or folders should be included in the response