Rename apiBasic to apiAccountsHashDifficulty

This commit is contained in:
Phil Davis
2021-01-28 11:56:07 +05:45
parent 5a44f83bbf
commit 924246c0a6
8 changed files with 51 additions and 33 deletions
+2 -2
View File
@@ -239,8 +239,8 @@ def testPipelines(ctx):
pipelines = [
localApiTests(ctx, 'owncloud', 'apiOcisSpecific'),
localApiTests(ctx, 'ocis', 'apiOcisSpecific'),
localApiTests(ctx, 'owncloud', 'apiBasic', 'default'),
localApiTests(ctx, 'ocis', 'apiBasic', 'default')
localApiTests(ctx, 'owncloud', 'apiAccountsHashDifficulty', 'default'),
localApiTests(ctx, 'ocis', 'apiAccountsHashDifficulty', 'default')
]
for runPart in range(1, config['apiTests']['numberOfParts'] + 1):
+2 -2
View File
@@ -3,9 +3,9 @@ default:
'': '%paths.base%/../features/bootstrap'
suites:
apiBasic:
apiAccountsHashDifficulty:
paths:
- '%paths.base%/../features/apiBasic'
- '%paths.base%/../features/apiAccountsHashDifficulty'
context: &common_ldap_suite_context
parameters:
ldapAdminPassword: admin
+8 -8
View File
@@ -51,11 +51,11 @@ help:
@echo -e "https://hub.docker.com/r/owncloud/ocis."
@echo
@echo -e "${GREEN}Run full oCIS test suites against oCIS with oCIS storage:${RESET}\n"
@echo -e "\tmake localApiTests-apiBasic-ocis\t\t${BLUE}run apiBasic test suite${RESET}"
@echo -e "\tmake localApiTests-apiAccountsHashDifficulty-ocis\t\t${BLUE}run apiAccountsHashDifficulty test suite${RESET}"
@echo -e "\tmake localApiTests-apiOcisSpecific-ocis\t\t${BLUE}run apiOcisSPecific test suite${RESET}"
@echo
@echo -e "${GREEN}Run full oCIS test suites against oCIS with ownCloud storage:${RESET}\n"
@echo -e "\tmake localApiTests-apiBasic-owncloud\t\t${BLUE}run apiBasic test suite${RESET}"
@echo -e "\tmake localApiTests-apiAccountsHashDifficulty-owncloud\t\t${BLUE}run apiAccountsHashDifficulty test suite${RESET}"
@echo -e "\tmake localApiTests-apiOcisSpecific-owncloud\t${BLUE}run apiOcisSpecific test suite${RESET}"
@echo
@echo -e "${GREEN}Run full ownCloud test suites against oCIS with oCIS storage:${RESET}\n"
@@ -133,11 +133,11 @@ localApiTests-apiOcisSpecific-owncloud: ## run apiOcisSpecific test suite with o
BEHAT_SUITE=apiOcisSpecific \
$(MAKE) --no-print-directory testSuite
.PHONY: localApiTests-apiBasic-owncloud
localApiTests-apiBasic-owncloud: ## run apiBasic test suite with owncloud storage
.PHONY: localApiTests-apiAccountsHashDifficulty-owncloud
localApiTests-apiAccountsHashDifficulty-owncloud: ## run apiAccountsHashDifficulty test suite with owncloud storage
@TEST_SOURCE=ocis \
STORAGE=owncloud \
BEHAT_SUITE=apiBasic \
BEHAT_SUITE=apiAccountsHashDifficulty \
$(MAKE) --no-print-directory testSuite
.PHONY: localApiTests-apiOcisSpecific-ocis
@@ -147,11 +147,11 @@ localApiTests-apiOcisSpecific-ocis: ## run apiOcisSPecific test suite with ocis
BEHAT_SUITE=apiOcisSpecific \
$(MAKE) --no-print-directory testSuite
.PHONY: localApiTests-apiBasic-ocis
localApiTests-apiBasic-ocis: ## run apiBasic test suite with ocis storage
.PHONY: localApiTests-apiAccountsHashDifficulty-ocis
localApiTests-apiAccountsHashDifficulty-ocis: ## run apiAccountsHashDifficulty test suite with ocis storage
@TEST_SOURCE=ocis \
STORAGE=ocis \
BEHAT_SUITE=apiBasic \
BEHAT_SUITE=apiAccountsHashDifficulty \
$(MAKE) --no-print-directory testSuite
targets = $(addprefix Core-API-Tests-owncloud-storage-,$(PARTS))
@@ -0,0 +1,21 @@
@api @provisioning_api-app-required @skipOnLDAP
Feature: add user
As an admin
I want to be able to add users and store their password with the full hash difficulty
So that I can give people controlled individual access to resources on the ownCloud server
Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production
See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839
Scenario Outline: admin creates a user
Given using OCS API version "<ocs_api_version>"
And user "brand-new-user" has been deleted
When the administrator sends a user creation request for user "brand-new-user" password "%alt1%" using the provisioning API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And user "brand-new-user" should exist
And user "brand-new-user" should be able to access a skeleton file
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |
@@ -1,5 +1,11 @@
@api @files_sharing-app-required
Feature: sharing
As a user
I want to be able to share files when passwords are stored with the full hash difficulty
So that I can give people secure controlled access to my data
Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production
See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839
Scenario Outline: Creating a share of a file with a user
Given the administrator has set the default folder for received shares to "Shares"
@@ -1,8 +1,11 @@
@api
Feature: upload file
As a user
I want to be able to upload files
So that I can store and share files between multiple client systems
I want to be able to upload files when passwords are stored with the full hash difficulty
So that I can store and share files securely between multiple client systems
Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production
See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839
Scenario Outline: upload a file and check download content
Given using OCS API version "<ocs_api_version>"
@@ -15,4 +18,4 @@ Feature: upload file
| 1 | old |
| 1 | new |
| 2 | old |
| 2 | new |
| 2 | new |
@@ -1,5 +1,11 @@
@api
Feature: attempt to PUT files with invalid password
As an admin
I want to the system to be secure when passwords are stored with the full hash difficulty
So that unauthorised users do not have access to data
Note - this feature is run in CI with ACCOUNTS_HASH_DIFFICULTY set to the default for production
See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839
Background:
Given user "Alice" has been created with default attributes and without skeleton files
@@ -1,18 +0,0 @@
@api @provisioning_api-app-required @skipOnLDAP
Feature: add user
As an admin
I want to be able to add users
So that I can give people controlled individual access to resources on the ownCloud server
Scenario Outline: admin creates a user
Given using OCS API version "<ocs_api_version>"
And user "brand-new-user" has been deleted
When the administrator sends a user creation request for user "brand-new-user" password "%alt1%" using the provisioning API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"
And user "brand-new-user" should exist
And user "brand-new-user" should be able to access a skeleton file
Examples:
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |