Refactor feature files to add proper description
This commit is contained in:
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: auth
|
||||
As a user
|
||||
I want to send delete request with wrong password
|
||||
So that I can make sure it doesn't work
|
||||
|
||||
Background:
|
||||
Given user "another-admin" has been created with default attributes and without skeleton files
|
||||
|
||||
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: auth
|
||||
As a user
|
||||
I want to send GET request to various endpoints
|
||||
So that I can make sure the endpoints need proper authentication
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
@@ -101,7 +104,7 @@ Feature: auth
|
||||
And the OCS status code of responses on all endpoints should be "200"
|
||||
|
||||
@issue-1319
|
||||
Scenario:using OCS with admin basic auth
|
||||
Scenario: using OCS with admin basic auth
|
||||
When the administrator requests these endpoint with "GET"
|
||||
| endpoint |
|
||||
| /ocs/v1.php/cloud/apps |
|
||||
|
||||
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: auth
|
||||
As a user
|
||||
I want to send POST request to various endpoints
|
||||
So that I can make sure the endpoints need proper authentication
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@@ -1,5 +1,8 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: auth
|
||||
As a user
|
||||
I want to send PUT request to various endpoints
|
||||
So that I can make sure the endpoints need proper authentication
|
||||
|
||||
Background:
|
||||
Given user "another-admin" has been created with default attributes and without skeleton files
|
||||
@@ -21,7 +24,7 @@ Feature: auth
|
||||
And the OCS status code of responses on all endpoints should be "997"
|
||||
|
||||
|
||||
Scenario: Request to edit nonexistent user by authorized admin gets unauthorized in http response
|
||||
Scenario: request to edit nonexistent user by authorized admin gets unauthorized in http response
|
||||
Given user "another-admin" has been added to group "admin"
|
||||
When user "another-admin" requests these endpoints with "PUT" including body "doesnotmatter" about user "nonexistent"
|
||||
| endpoint |
|
||||
|
||||
Reference in New Issue
Block a user