[tests-only][full-ci] adding user quota using graph api instead of Provisioning api (#7000)
* refactored getQuota scenario * deleted quota step inside provisioning file * updating feature file of quota as per graphapi * updated expected failures file * updated expected failures file * removed issue tag
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
@issue-1313 @skipOnGraph
|
||||
@issue-1313 @skipOnReva
|
||||
Feature: get quota
|
||||
As a user
|
||||
I want to be able to find out my available storage quota
|
||||
@@ -11,9 +11,9 @@ Feature: get quota
|
||||
|
||||
Scenario Outline: retrieving folder quota when no quota is set
|
||||
Given using <dav-path-version> DAV path
|
||||
When the administrator gives unlimited quota to user "Alice" using the provisioning API
|
||||
When user "Admin" changes the quota of the "Alice Hansen" space to "0"
|
||||
Then the HTTP status code should be "200"
|
||||
And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "-3"
|
||||
And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "0"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -23,66 +23,67 @@ Feature: get quota
|
||||
@smokeTest
|
||||
Scenario Outline: retrieving folder quota when quota is set
|
||||
Given using <dav-path-version> DAV path
|
||||
When the administrator sets the quota of user "Alice" to "10 MB" using the provisioning API
|
||||
When user "Admin" changes the quota of the "Alice Hansen" space to "10000"
|
||||
Then the HTTP status code should be "200"
|
||||
And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "10485406"
|
||||
And as user "Alice" folder "/" should contain a property "d:quota-available-bytes" with value "10000"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
|
||||
@issue-8197
|
||||
Scenario Outline: retrieving folder quota of shared folder with quota when no quota is set for recipient
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has been given unlimited quota
|
||||
And the quota of user "Brian" has been set to "10 MB"
|
||||
And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "0"
|
||||
And user "Admin" has changed the quota of the personal space of "Brian Murphy" space to "10000"
|
||||
And user "Brian" has created folder "/testquota"
|
||||
And user "Brian" has uploaded file "/testquota/Brian.txt" of size 1000 bytes
|
||||
And user "Brian" has created a share with settings
|
||||
| path | testquota |
|
||||
| shareType | user |
|
||||
| permissions | all |
|
||||
| shareWith | Alice |
|
||||
When user "Alice" gets the following properties of folder "/testquota" using the WebDAV API
|
||||
When user "Alice" gets the following properties of folder "<folder-path>" inside space "Shares" using the WebDAV API
|
||||
| propertyName |
|
||||
| d:quota-available-bytes |
|
||||
Then the HTTP status code should be "200"
|
||||
And the single response should contain a property "d:quota-available-bytes" with value "10485406"
|
||||
Then the HTTP status code should be "207"
|
||||
And the single response should contain a property "d:quota-available-bytes" with value "9000"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
| dav-path-version | folder-path |
|
||||
| old | /Shares/testquota |
|
||||
| new | /Shares/testquota |
|
||||
| spaces | /testquota |
|
||||
|
||||
@issue-8197
|
||||
Scenario Outline: retrieving folder quota when quota is set and a file was uploaded
|
||||
Given using <dav-path-version> DAV path
|
||||
And the quota of user "Alice" has been set to "1 KB"
|
||||
And user "Alice" has uploaded file "/prueba.txt" of size 93 bytes
|
||||
And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "10000"
|
||||
And user "Alice" has uploaded file "/prueba.txt" of size 1000 bytes
|
||||
When user "Alice" gets the following properties of folder "/" using the WebDAV API
|
||||
| propertyName |
|
||||
| d:quota-available-bytes |
|
||||
Then the HTTP status code should be "201"
|
||||
And the single response should contain a property "d:quota-available-bytes" with value "577"
|
||||
Then the HTTP status code should be "207"
|
||||
And the single response should contain a property "d:quota-available-bytes" with value "9000"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@skipOnReva
|
||||
|
||||
Scenario Outline: retrieving folder quota when quota is set and a file was received
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And the quota of user "Brian" has been set to "1 KB"
|
||||
And user "Admin" has changed the quota of the personal space of "Brian Murphy" space to "10000"
|
||||
And user "Alice" has uploaded file "/Alice.txt" of size 93 bytes
|
||||
And user "Alice" has shared file "Alice.txt" with user "Brian"
|
||||
When user "Brian" gets the following properties of folder "/" using the WebDAV API
|
||||
| propertyName |
|
||||
| d:quota-available-bytes |
|
||||
Then the HTTP status code should be "200"
|
||||
And the single response should contain a property "d:quota-available-bytes" with value "670"
|
||||
Then the HTTP status code should be "207"
|
||||
And the single response should contain a property "d:quota-available-bytes" with value "10000"
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
|
||||
Reference in New Issue
Block a user