Skip to content

Adjust create user steps #98

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

Merged
phil-davis merged 1 commit into from
Jun 7, 2019
Merged

Adjust create user steps #98

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 6 additions & 6 deletions tests/acceptance/features/apiTestingApp/lockProvisioning.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Feature: add and delete locks on files
Scenario Outline: admin locks a file for a user
Given using OCS API version "<ocs-api-version>"
And locking has been enabled
And user "user0" has been created with default attributes
And user "user0" has been created with default attributes and skeleton files
When the administrator creates a lock for the file "textfile0.txt" with the type "1" for user "user0"
And the administrator checks the lock for the file "textfile0.txt" with the type "1" for user "user0"
Then the HTTP status code should be "<http-status>"
Expand All @@ -42,7 +42,7 @@ Feature: add and delete locks on files
Scenario Outline: admin deletes lock from a file for a user
Given using OCS API version "<ocs-api-version>"
And locking has been enabled
And user "user0" has been created with default attributes
And user "user0" has been created with default attributes and skeleton files
And the administrator has created a lock for the file "textfile0.txt" with the type "1" for user "user0"
When the administrator deletes the lock of the file "textfile0.txt" with the type "1" for user "user0"
And the administrator checks the lock for the file "textfile0.txt" with the type "1" for user "user0"
Expand All @@ -57,8 +57,8 @@ Feature: add and delete locks on files
Scenario Outline: admin releases all locks of one type
Given using OCS API version "<ocs-api-version>"
And locking has been enabled
And user "user0" has been created with default attributes
And user "user1" has been created with default attributes
And user "user0" has been created with default attributes and skeleton files
And user "user1" has been created with default attributes and skeleton files
And the administrator has created following locks
| path | type | user |
| textfile0.txt | 1 | user0 |
Expand All @@ -85,8 +85,8 @@ Feature: add and delete locks on files
Scenario Outline: admin releases all locks
Given using OCS API version "<ocs-api-version>"
And locking has been enabled
And user "user0" has been created with default attributes
And user "user1" has been created with default attributes
And user "user0" has been created with default attributes and skeleton files
And user "user1" has been created with default attributes and skeleton files
And the administrator has created following locks
| path | type | user |
| textfile0.txt | 1 | user0 |
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiTestingApp/notifications.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Feature: Test notifications feature of testing app

Background:
Given app "notifications" has been enabled
And these users have been created with default attributes:
And these users have been created with default attributes and skeleton files:
| username |
| user0 |
| user1 |
Expand Down