diff --git a/tests/ctst/features/quotas/Quotas.feature b/tests/ctst/features/quotas/Quotas.feature index dc6cd928cb..b653bfac51 100644 --- a/tests/ctst/features/quotas/Quotas.feature +++ b/tests/ctst/features/quotas/Quotas.feature @@ -52,36 +52,6 @@ Feature: Quota Management for APIs | UploadPart | 10 | 99 | 99 | IAM_USER | fail | QuotaExceeded | | UploadPart | 10 | 101 | 101 | IAM_USER | succeed | | - @2.6.0 - @PreMerge - @Quotas - @CronJob - @Restore - Scenario Outline: Object restoration (fake) implements strict quotas - Given an action "RestoreObject" - And an upload size of B for the object "" - And a "STORAGE_MANAGER" type - And a bucket quota set to B - And an account quota set to B - And a "" type - And an environment setup for the API - And an "existing" IAM Policy that "applies" with "ALLOW" effect for the current API - And the user tries to perform the current S3 action on the bucket 1 times with a 0 ms delay - Then the API should "" with "" - - Examples: - | uploadSize | bucketQuota | accountQuota | userType | result | expectedError | - | 100 | 0 | 0 | ACCOUNT | succeed | | - | 100 | 99 | 0 | ACCOUNT | fail | QuotaExceeded | - | 100 | 0 | 99 | ACCOUNT | fail | QuotaExceeded | - | 100 | 99 | 99 | ACCOUNT | fail | QuotaExceeded | - | 100 | 101 | 101 | ACCOUNT | succeed | | - | 100 | 0 | 0 | IAM_USER | succeed | | - | 100 | 99 | 0 | IAM_USER | fail | QuotaExceeded | - | 100 | 0 | 99 | IAM_USER | fail | QuotaExceeded | - | 100 | 99 | 99 | IAM_USER | fail | QuotaExceeded | - | 100 | 101 | 101 | IAM_USER | succeed | | - @2.6.0 @PreMerge @Quotas