Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Tests-Only] Skip on encryption more test scenarios #36988

Merged
merged 2 commits into from
Feb 20, 2020
Merged

[Tests-Only] Skip on encryption more test scenarios #36988

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a842d7
skipOnEncryptionType:user-keys for issue-encryption-181
phil-davis Feb 20, 2020
52d3866
skipOnEncryptionType:user-keys for issue-encryption-182
phil-davis Feb 20, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions tests/acceptance/features/cliLocalStorage/createLocalStorageForUsers.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ Feature: create local storage from the command line
| user0 |
| user1 |

@skipOnEncryptionType:user-keys @issue-encryption-181
Scenario: create local storages that are available to specific users
Given the administrator has created the local storage mount "local_storage2"
And the administrator has created the local storage mount "local_storage3"
Expand All @@ -34,6 +35,7 @@ Feature: create local storage from the command line
And the content of file "/local_storage3/file-in-local-storage3.txt" for user "user1" should be "this is a file in local storage3"
But as "user1" folder "/local_storage2" should not exist

@skipOnEncryptionType:user-keys @issue-encryption-181
Scenario: create local storage that is available for more than one user
And these users have been created with default attributes and without skeleton files:
| username |
Expand Down
4 changes: 4 additions & 0 deletions tests/acceptance/features/cliMain/filesChecksum.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,23 @@
@cli @local_storage @TestAlsoOnExternalUserBackend
Feature: files checksum command

@skipOnEncryptionType:user-keys @issue-encryption-182
Scenario: Administrator verifies the checksum of all the files
When the administrator invokes occ command "files:checksum:verify"
Then the command should have been successful

@skipOnEncryptionType:user-keys @issue-encryption-182
Scenario: Administrator fixes the mismatched checksums
When the administrator invokes occ command "files:checksum:verify -r"
Then the command should have been successful

@skipOnEncryptionType:user-keys @issue-encryption-182
Scenario: Administrator verifies the checksum of all the files of a user
Given user "user0" has been created with default attributes and skeleton files
When the administrator invokes occ command "files:checksum:verify --user=user0"
Then the command should have been successful

@skipOnEncryptionType:user-keys @issue-encryption-182
Scenario: Administrator fixes the mismatched checksums of all the files of a user
Given user "user0" has been created with default attributes and skeleton files
When the administrator invokes occ command "files:checksum:verify -r --user=user0"
Expand Down