Skip to content

Commit

Permalink
[Tests-Only] skip and tag tests for EOS
Browse files Browse the repository at this point in the history
  • Loading branch information
dpakach committed Jun 29, 2020
1 parent 1695336 commit a0c654e
Show file tree
Hide file tree
Showing 10 changed files with 92 additions and 27 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Feature: get file info using PROPFIND
| /remote.php/dav/files/%username%/PARENT | 404 | <?xml version="1.0"?><d:propfind xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns"><d:prop><d:getetag /></d:prop></d:propfind> |
| /remote.php/dav/files/%username%/PARENT/parent.txt | 404 | <?xml version="1.0"?><d:propfind xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns"><d:prop><d:getetag /></d:prop></d:propfind> |

@skipOnOcV10 @issue-ocis-reva-9
@skipOnOcV10 @issue-ocis-reva-9 @skipOnOcis-EOS-Storage @issue-ocis-reva-303
#after fixing all issues delete this Scenario and use the one above
Scenario: send PROPFIND requests to another user's webDav endpoints as normal user
When user "Brian" requests these endpoints with "PROPFIND" including body then the status codes about user "Alice" should be as listed
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ Feature: cannot share resources with invalid permissions
And the HTTP status code should be "<http_status_code_ocs>" or "<http_status_code_eos>"
And as "Brian" entry "textfile0.txt" should not exist
Examples:
| ocs_api_version | ocs_status_code | ocs_status_code | http_status_code_ocs | http_status_code_eos | permissions |
| ocs_api_version | eos_status_code | ocs_status_code | http_status_code_ocs | http_status_code_eos | permissions |
| 1 | 100 | 996 | 200 | 500 | delete |
| 2 | 200 | 996 | 200 | 500 | delete |
| 1 | 100 | 996 | 200 | 500 | create,delete |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -289,7 +289,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |

@skipOnOcis-OC-Storage @issue-ocis-reva-21 @issue-ocis-reva-243
@skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243
Scenario Outline: sharing subfolder of already shared folder, GET result is correct
Given using OCS API version "<ocs_api_version>"
And these users have been created with default attributes and without skeleton files:
Expand Down Expand Up @@ -319,7 +319,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |

@skipOnOcis-OC-Storage @issue-ocis-reva-14 @issue-ocis-reva-243
@skipOnOcis @issue-ocis-reva-14 @issue-ocis-reva-243
Scenario Outline: user shares a file with file name longer than 64 chars to another user
Given using OCS API version "<ocs_api_version>"
And user "Brian" has been created with default attributes and without skeleton files
Expand All @@ -333,7 +333,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |

@skipOnOcis-OC-Storage @issue-ocis-reva-21 @issue-ocis-reva-243
@skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243
Scenario Outline: user shares a file with file name longer than 64 chars to a group
Given using OCS API version "<ocs_api_version>"
And group "grp1" has been created
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Feature: sharing
| Alice |
| Brian |

@smokeTest @skipOnOcis-EOS-Storage
@smokeTest
Scenario Outline: Sharee can see the share
Given using OCS API version "<ocs_api_version>"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
Expand All @@ -20,7 +20,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |

@smokeTest @skipOnOcis-EOS-Storage
@smokeTest
Scenario Outline: Sharee can see the filtered share
Given using OCS API version "<ocs_api_version>"
And user "Alice" has shared file "textfile0.txt" with user "Brian"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ Feature: sharing
And as "Alice" folder "/Alice-folder/folder2" should not exist
And as "Carol" folder "/Carol-folder/folder2" should exist

@skipOnOcV10 @skipOnOcis-EOS-Storage
@skipOnOcV10
Scenario: cannot get information of a specific share
Given these users have been created with default attributes and without skeleton files:
| username |
Expand Down
2 changes: 1 addition & 1 deletion tests/acceptance/features/apiVersions/fileVersions.feature
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
@api @files_versions-app-required @TestAlsoOnExternalUserBackend
@api @files_versions-app-required @TestAlsoOnExternalUserBackend @skipOnOcis-EOS-Storage

Feature: dav-versions

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ Feature: previews of files downloaded through the webdav API
And the value of the item "/d:error/s:message" in the response about user "Alice" should be "File not found: parent.txt in '%username%'"
And the value of the item "/d:error/s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound"

@skipOnOcV10 @issue-ocis-thumbnails-191
@skipOnOcV10 @issue-ocis-thumbnails-191 @skipOnOcis-EOS-Storage @issue-ocis-reva-308
#after fixing all issues delete this Scenario and use the one above
Scenario: download previews of other users files
Given user "Brian" has been created with default attributes and without skeleton files
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Feature: create folder
| old |
| new |

@skipOnOcis @issue-ocis-reva-168 @skipOnOcis-EOS-Storage @issue-ocis-reva-269
@skipOnOcis @issue-ocis-reva-168
Scenario Outline: try to create a folder that already exists
Given using <dav_version> DAV path
And user "Alice" has created folder "my-data"
Expand All @@ -85,7 +85,7 @@ Feature: create folder
| old |
| new |

@skipOnOcV10 @issue-ocis-reva-168
@skipOnOcV10 @issue-ocis-reva-168 @skipOnOcis-EOS-Storage
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: try to create a folder that already exists
Given using <dav_version> DAV path
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Feature: get file properties
| new | /file ?2.txt | dav\/files\/%username%\/file%20%3f2\.txt |
| new | /file &2.txt | dav\/files\/%username%\/file%20%262\.txt |

@skipOnOcV10 @issue-ocis-reva-214 @issue-ocis-reva-265 @skipOnOcis-EOS-Storage
@skipOnOcV10 @issue-ocis-reva-214
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: Do a PROPFIND of various file names
Given using <dav_version> DAV path
Expand All @@ -53,15 +53,26 @@ Feature: get file properties
| dav_version | file_name | expected_href |
| old | /C++ file.cpp | webdav\/C\+\+%20file\.cpp |
| old | /file #2.txt | webdav\/file%20%232\.txt |
| old | /file ?2.txt | webdav\/file%20%3F2\.txt |
| old | /file &2.txt | webdav\/file%20&2\.txt |
| new | /C++ file.cpp | dav\/files\/%username%\/C\+\+%20file\.cpp |
| new | /file #2.txt | dav\/files\/%username%\/file%20%232\.txt |
| new | /file ?2.txt | dav\/files\/%username%\/file%20%3F2\.txt |
| new | /file &2.txt | dav\/files\/%username%\/file%20&2\.txt |

@skipOnOcV10 @issue-ocis-reva-214 @issue-ocis-reva-265 @skipOnOcis-EOS-Storage
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: Do a PROPFIND of various file names
Given using <dav_version> DAV path
And user "Alice" has uploaded file with content "uploaded content" to "<file_name>"
When user "Alice" gets the properties of file "<file_name>" using the WebDAV API
Then the properties response should contain an etag
And the value of the item "//d:response/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>/"
Examples:
| dav_version | file_name | expected_href |
| old | /file ?2.txt | webdav\/file%20%3F2\.txt |
| new | /file ?2.txt | dav\/files\/%username%\/file%20%3F2\.txt |

@skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcV10
#after fixing the issues merge this Scenario into the one above
#after fixing the issues delete this Scenario
Scenario Outline: upload a file to content
Given using <dav_version> DAV path
When user "Alice" uploads file with content "uploaded content" to "<file_name>" using the WebDAV API
Expand Down Expand Up @@ -98,7 +109,7 @@ Feature: get file properties
| new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3f2\.txt |
| new | /folder &2.txt | dav\/files\/%username%\/folder%20%262\.txt |

@skipOnOcV10 @issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265
@skipOnOcV10 @issue-ocis-reva-214
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path
Expand All @@ -116,17 +127,43 @@ Feature: get file properties
| old | /C++ folder | webdav\/C\+\+%20folder |
| old | /नेपाली | webdav\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 |
| old | /folder #2.txt | webdav\/folder%20%232\.txt |
| old | /folder ?2.txt | webdav\/folder%20%3F2\.txt |
| old | /folder &2.txt | webdav\/folder%20&2\.txt |
| new | /upload | dav\/files\/%username%\/upload |
| new | /strängé folder | dav\/files\/%username%\/str%C3%A4ng%C3%A9%20folder |
| new | /C++ folder | dav\/files\/%username%\/C\+\+%20folder |
| new | /नेपाली | dav\/files\/%username%\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 |
| new | /folder #2.txt | dav\/files\/%username%\/folder%20%232\.txt |
| new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt |
| new | /folder &2.txt | dav\/files\/%username%\/folder%20&2\.txt |

@skipOnOcis-EOS-Storage @issue-ocis-reva-265
@skipOnOcV10 @issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path
And user "Alice" has created folder "<folder_name>"
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file1.txt"
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file2.txt"
When user "Alice" gets the properties of folder "<folder_name>" with depth 1 using the WebDAV API
Then the value of the item "//d:response[1]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\//"
And the value of the item "//d:response[2]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file1.txt/"
And the value of the item "//d:response[3]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file2.txt/"
Examples:
| dav_version | folder_name | expected_href |
| old | /folder ?2.txt | webdav\/folder%20%3F2\.txt |
| new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt |

@skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcV10
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path
And user "Alice" has created folder "/folder ?2.txt"
When user "Alice" uploads to these filenames with content "uploaded content" using the webDAV API then the results should be as listed
| filename | http-code | exists |
| /folder ?2.txt/file1.txt | 500 | no |
Examples:
| dav_version |
| old |
| new |

Scenario Outline: Do a PROPFIND of various files inside various folders
Given using <dav_version> DAV path
And user "Alice" has created folder "<folder_name>"
Expand All @@ -140,12 +177,23 @@ Feature: get file properties
| old | /C++ folder | C++ file.cpp |
| old | /नेपाली | नेपाली |
| old | /folder #2.txt | file #2.txt |
| old | /folder ?2.txt | file ?2.txt |
| new | /upload | abc.txt |
| new | /strängé folder (duplicate #2 &) | strängé file (duplicate #2 &) |
| new | /C++ folder | C++ file.cpp |
| new | /नेपाली | नेपाली |
| new | /folder #2.txt | file #2.txt |

@skipOnOcis-EOS-Storage @issue-ocis-reva-265
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: Do a PROPFIND of various files inside various folders
Given using <dav_version> DAV path
And user "Alice" has created folder "<folder_name>"
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/<file_name>"
When user "Alice" gets the properties of file "<folder_name>/<file_name>" using the WebDAV API
Then the properties response should contain an etag
Examples:
| dav_version | folder_name | file_name |
| old | /folder ?2.txt | file ?2.txt |
| new | /folder ?2.txt | file ?2.txt |

Scenario Outline: A file that is not shared does not have a share-types property
Expand Down
29 changes: 23 additions & 6 deletions tests/acceptance/features/apiWebdavUpload1/uploadFile.feature
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,6 @@ Feature: upload file
| new | /strängé file.txt |
| new | /नेपाली.txt |

@skipOnOcis-EOS-Storage @issue-ocis-reva-265
Scenario Outline: upload a file and check download content
Given using <dav_version> DAV path
When user "Alice" uploads file with content "uploaded content" to <file_name> using the WebDAV API
Expand All @@ -33,11 +32,20 @@ Feature: upload file
| dav_version | file_name |
| old | "C++ file.cpp" |
| old | "file #2.txt" |
| new | "C++ file.cpp" |
| new | "file #2.txt" |

@skipOnOcis-EOS-Storage @issue-ocis-reva-265
#after fixing all issues delete this Scenario and merge with the one above
Scenario Outline: upload a file and check download content
Given using <dav_version> DAV path
When user "Alice" uploads file with content "uploaded content" to <file_name> using the WebDAV API
Then the content of file <file_name> for user "Alice" should be "uploaded content"
Examples:
| dav_version | file_name |
| old | "file ?2.txt" |
| old | " ?fi=le&%#2 . txt" |
| old | " # %ab ab?=ed " |
| new | "C++ file.cpp" |
| new | "file #2.txt" |
| new | "file ?2.txt" |
| new | " ?fi=le&%#2 . txt" |
| new | " # %ab ab?=ed " |
Expand All @@ -53,7 +61,6 @@ Feature: upload file
| old | "file ?2.txt" |
| new | "file ?2.txt" |

@skipOnOcis-EOS-Storage @issue-ocis-reva-265
Scenario Outline: upload a file into a folder and check download content
Given using <dav_version> DAV path
And user "Alice" has created folder "<folder_name>"
Expand All @@ -66,13 +73,23 @@ Feature: upload file
| old | /C++ folder | C++ file.cpp |
| old | /नेपाली | नेपाली |
| old | /folder #2.txt | file #2.txt |
| old | /folder ?2.txt | file ?2.txt |
| old | /?fi=le&%#2 . txt | # %ab ab?=ed |
| new | /upload | abc.txt |
| new | /strängé folder (duplicate #2 &) | strängé file (duplicate #2 &) |
| new | /C++ folder | C++ file.cpp |
| new | /नेपाली | नेपाली |
| new | /folder #2.txt | file #2.txt |

@skipOnOcis-EOS-Storage @issue-ocis-reva-265
#after fixing all issues delete this Scenario and use the one above
Scenario Outline: upload a file into a folder and check download content
Given using <dav_version> DAV path
And user "Alice" has created folder "<folder_name>"
When user "Alice" uploads file with content "uploaded content" to "<folder_name>/<file_name>" using the WebDAV API
Then the content of file "<folder_name>/<file_name>" for user "Alice" should be "uploaded content"
Examples:
| dav_version | folder_name | file_name |
| old | /folder ?2.txt | file ?2.txt |
| old | /?fi=le&%#2 . txt | # %ab ab?=ed |
| new | /folder ?2.txt | file ?2.txt |
| new | /?fi=le&%#2 . txt | # %ab ab?=ed |

Expand Down

0 comments on commit a0c654e

Please sign in to comment.