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] Adjust skip tags expected failures #37725

Closed
wants to merge 1 commit into from
Closed

[Tests-Only] Adjust skip tags expected failures #37725

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
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiAuth/cors.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@api @skipOnOcis @issue-ocis-reva-26 @issue-ocis-reva-27
@api @wasSkipOnOcis @issue-ocis-reva-26 @issue-ocis-reva-27
Feature: CORS headers

Background:
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiAuth/filesAppAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@api @skipOnOcis @issue-ocis-reva-28
@api @skipOnOcis @notToImplementOnOCIS @issue-ocis-reva-28
Feature: auth

Background:
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiAuth/tokenAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@api @skipOnOcis @issue-ocis-reva-28 @issue-ocis-reva-37
@api @skipOnOcis @notToImplementOnOCIS @issue-ocis-reva-28 @issue-ocis-reva-37
Feature: tokenAuth

Background:
Expand Down
4 changes: 2 additions & 2 deletions tests/acceptance/features/apiAuth/webDavAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Feature: auth
When user "Alice" requests "/remote.php/webdav" with "PROPFIND" using basic auth
Then the HTTP status code should be "207"

@smokeTest @skipOnOcis @issue-ocis-reva-28
@smokeTest @skipOnOcis @notToImplementOnOCIS @issue-ocis-reva-28
Scenario: using WebDAV with token auth
Given a new client token for "Alice" has been generated
When user "Alice" requests "/remote.php/webdav" with "PROPFIND" using basic token auth
Expand All @@ -25,7 +25,7 @@ Feature: auth
# When requesting "/remote.php/webdav" with "PROPFIND" using a client token
# Then the HTTP status code should be "207"

@smokeTest @skipOnOcis
@smokeTest @skipOnOcis @toImplementOnOCIS
Scenario: using WebDAV with browser session
Given a new browser session for "Alice" has been started
When the user requests "/remote.php/webdav" with "PROPFIND" using the browser session
Expand Down
4 changes: 2 additions & 2 deletions tests/acceptance/features/apiAuthOcs/ocsDELETEAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
@api @files_sharing-app-required @skipOnOcis
@api @files_sharing-app-required @wasSkipOnOcis
Feature: auth

Background:
Given user "another-admin" has been created with default attributes and without skeleton files
And user "another-admin" has been added to group "admin"

@smokeTest @issue-32068 @skipOnOcis @issue-ocis-reva-30 @issue-ocis-reva-65
@smokeTest @issue-32068 @wasSkipOnOcis @issue-ocis-reva-30 @issue-ocis-reva-65
@skipOnBruteForceProtection @issue-brute_force_protection-112
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When user "another-admin" requests these endpoints with "DELETE" using password "invalid" about user "Alice"
Expand Down
18 changes: 9 additions & 9 deletions tests/acceptance/features/apiAuthOcs/ocsGETAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Feature: auth
Background:
Given user "Alice" has been created with default attributes and skeleton files

@issue-32068 @skipOnOcis
@issue-32068 @wasSkipOnOcis
@issue-ocis-reva-30
@smokeTest
Scenario: using OCS anonymously
Expand All @@ -29,7 +29,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "997"

@skipOnOcis @issue-ocis-reva-29
@wasSkipOnOcis @issue-ocis-reva-29
Scenario: ocs config end point accessible by unauthorized users
When a user requests these endpoints with "GET" and no authentication
| endpoint |
Expand Down Expand Up @@ -71,7 +71,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"

@issue-32068 @skipOnOcis
@issue-32068 @wasSkipOnOcis
@issue-ocis-reva-11
@issue-ocis-reva-30
@issue-ocis-reva-31
Expand Down Expand Up @@ -165,7 +165,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"

@issue-32068 @skipOnOcis
@issue-32068 @wasSkipOnOcis
@issue-ocis-reva-29
@issue-ocis-reva-30
@smokeTest
Expand Down Expand Up @@ -232,7 +232,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"

@skipOnOcis
@wasSkipOnOcis
@issue-ocis-reva-65
Scenario:using OCS with admin basic auth
When the administrator requests these endpoint with "GET"
Expand All @@ -250,7 +250,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"

@skipOnOcis
@wasSkipOnOcis
@issue-ocis-reva-30
@issue-ocis-reva-65
@skipOnBruteForceProtection @issue-brute_force_protection-112
Expand Down Expand Up @@ -289,7 +289,7 @@ Feature: auth
And the OCS status code of responses on all endpoints should be "200"


@skipOnOcis
@wasSkipOnOcis
@issue-ocis-reva-30
@issue-ocis-reva-28
Scenario: using OCS with token auth of a normal user
Expand Down Expand Up @@ -325,7 +325,7 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "997"

@skipOnOcis
@skipOnOcis @toImplementOnOCIS
Scenario: using OCS with browser session of normal user
Given a new browser session for "Alice" has been started
When the user requests these endpoints with "GET" using a new browser session
Expand Down Expand Up @@ -360,7 +360,7 @@ Feature: auth
And the OCS status code of responses on all endpoints should be "997"


@skipOnOcis
@skipOnOcis @notToImplementOnOCIS
@issue-ocis-reva-30
@issue-ocis-reva-60
Scenario: using OCS with an app password of a normal user
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiAuthOcs/ocsPOSTAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Feature: auth
Background:
Given user "Alice" has been created with default attributes and skeleton files

@skipOnOcis
@wasSkipOnOcis
@issue-ocis-reva-30
@smokeTest
@skipOnBruteForceProtection @issue-brute_force_protection-112
Expand Down
4 changes: 2 additions & 2 deletions tests/acceptance/features/apiAuthOcs/ocsPUTAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
@api @files_sharing-app-required @skipOnOcis
@api @files_sharing-app-required @wasSkipOnOcis
Feature: auth

Background:
Given user "another-admin" has been created with default attributes and without skeleton files
And user "another-admin" has been added to group "admin"

@skipOnOcis
@wasSkipOnOcis
@issue-ocis-reva-30
@smokeTest
@skipOnBruteForceProtection @issue-brute_force_protection-112
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavDELETEAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Feature: delete file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-13
@wasSkipOnOcis @issue-ocis-reva-13
Scenario: send DELETE requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "DELETE" including body "doesnotmatter" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -74,7 +74,7 @@ Feature: delete file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-60
@wasSkipOnOcis @issue-ocis-reva-60
Scenario: send DELETE requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -88,7 +88,7 @@ Feature: delete file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-60
@wasSkipOnOcis @issue-ocis-reva-60
Scenario: send DELETE requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavLOCKAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Feature: LOCK file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-9
@wasSkipOnOcis @issue-ocis-reva-9
Scenario: send LOCK requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "LOCK" to get property "d:shared" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -88,7 +88,7 @@ Feature: LOCK file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send LOCK requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -102,7 +102,7 @@ Feature: LOCK file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send LOCK requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-9 @issue-ocis-reva-197
@wasSkipOnOcis @issue-ocis-reva-9 @issue-ocis-reva-197
Scenario: send MKCOL requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -78,7 +78,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send MKCOL requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -92,7 +92,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send MKCOL requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavMOVEAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Feature: MOVE file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-14
@wasSkipOnOcis @issue-ocis-reva-14
Scenario: send MOVE requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "MOVE" including body "doesnotmatter" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -84,7 +84,7 @@ Feature: MOVE file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send MOVE requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -98,7 +98,7 @@ Feature: MOVE file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send MOVE requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Feature: get file info using POST
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-179
@wasSkipOnOcis @issue-ocis-reva-179
Scenario: send POST requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "POST" including body "doesnotmatter" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -75,7 +75,7 @@ Feature: get file info using POST
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send POST requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -89,7 +89,7 @@ Feature: get file info using POST
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send POST requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavPROPFINDAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Feature: get file info using PROPFIND
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-9
@wasSkipOnOcis @issue-ocis-reva-9
Scenario: send PROPFIND requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "PROPFIND" to get property "d:getetag" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -84,7 +84,7 @@ Feature: get file info using PROPFIND
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send PROPFIND requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -98,7 +98,7 @@ Feature: get file info using PROPFIND
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send PROPFIND requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-9 @issue-ocis-reva-197
@wasSkipOnOcis @issue-ocis-reva-9 @issue-ocis-reva-197
Scenario: send PROPPATCH requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "PROPPATCH" to set property "favorite" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -75,7 +75,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send PROPPATCH requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -89,7 +89,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send PROPPATCH requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
6 changes: 3 additions & 3 deletions tests/acceptance/features/apiAuthWebDav/webDavPUTAuth.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Feature: get file info using PUT
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-9 @issue-ocis-reva-197
@wasSkipOnOcis @issue-ocis-reva-9 @issue-ocis-reva-197
Scenario: send PUT requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "PUT" including body "doesnotmatter" about user "Alice"
| endpoint |
Expand Down Expand Up @@ -78,7 +78,7 @@ Feature: get file info using PUT
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send PUT requests to webDav endpoints using token authentication should not work
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand All @@ -92,7 +92,7 @@ Feature: get file info using PUT
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"

@skipOnOcis @issue-ocis-reva-37
@wasSkipOnOcis @issue-ocis-reva-37
Scenario: send PUT requests to webDav endpoints using app password token as password
Given token auth has been enforced
And a new browser session for "Alice" has been started
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiCapabilities/capabilities.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@api @files_sharing-app-required @skipOnOcis @issue-ocis-reva-41
@api @files_sharing-app-required @wasSkipOnOcis @issue-ocis-reva-41
Feature: capabilities

Background:
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiCapabilities/capabilitiesWithNormalUser.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ Feature: default capabilities for normal user

# remove this scenario after fixing tagged issue as its just created to show difference
# in the response items in different environment (core & ocis-reva)
@skipOnOcis @issue-ocis-reva-175 @issue-ocis-reva-176
@wasSkipOnOcis @issue-ocis-reva-175 @issue-ocis-reva-176
Scenario: getting default capabilities with normal user
When user "Alice" retrieves the capabilities using the capabilities API
Then the capabilities should contain
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiComments/comments.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@api @comments-app-required @skipOnOcis @issue-ocis-reva-38
@api @comments-app-required @wasSkipOnOcis @issue-ocis-reva-38
Feature: Comments

Background:
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiComments/createComments.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@api @comments-app-required @files_sharing-app-required @skipOnOcis @issue-ocis-reva-38
@api @comments-app-required @files_sharing-app-required @wasSkipOnOcis @issue-ocis-reva-38
Feature: Comments

Background:
Expand Down
Loading