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.

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

add spaces WebDAV URL as a third variant for WebDAV path #2854

Closed
individual-it opened this issue Dec 9, 2021 · 3 comments · Fixed by owncloud/core#39599
Closed

add spaces WebDAV URL as a third variant for WebDAV path #2854

individual-it opened this issue Dec 9, 2021 · 3 comments · Fixed by owncloud/core#39599
Assignees
Labels
Priority:p2-high Escalation, on top of current planning, release blocker QA:team

Comments

@individual-it
Copy link
Member

Part of #2808

currently we use old and the new WebDAV path in the tests
old: remote.php/webdav
new: remote.php/dav/files/<username>

now we also need to run the tests with the new spaces concept.
The "private" space should react the same as the other WebDAV urls /dav/spaces/<uuid>/

The Example tables of the webdav related tests need to get an extra line. e.g.

  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         | "C++ file.cpp" |
      | old         | "file #2.txt"  |
      | new         | "C++ file.cpp" |
      | new         | "file #2.txt"  |

    @skipOnOcV10
    Examples:
      | spaces      | "C++ file.cpp" |
      | spaces      | "file #2.txt"  |

@Talank
Copy link
Contributor

Talank commented Jan 4, 2022

@amrita-shrestha is looking into this issue

@kiranparajuli589
Copy link
Contributor

kiranparajuli589 commented Jan 24, 2022

TODO:

Note: Please create a separate issue when you're taking one of the suites from above todo, link that issue with the correct suite, and properly (check/uncheck) boxes after that. Also, mark your in-progress suites, so that others will not start working on that.

@kiranparajuli589
Copy link
Contributor

the mentioned todo is finished 🥳 🎆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p2-high Escalation, on top of current planning, release blocker QA:team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants