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

fix API acceptance test steps, so that they really use old/new webdav path #32510

Closed
4 tasks done
individual-it opened this issue Aug 30, 2018 · 2 comments
Closed
4 tasks done

Comments

@individual-it
Copy link
Member

individual-it commented Aug 30, 2018

this steps only use the old webdav and not obeying what is said in Given using <dav_version> DAV path

  • @When /^the public downloads the last public shared file with range "([^"]*)" using the old WebDAV API$/
  • @When /^the public downloads file "([^"]*)" from inside the last public shared folder with range "([^"]*)" using the old WebDAV API$/
  • @When /^the public downloads file "([^"]*)" from inside the last public shared folder with password "([^"]*)" with range "([^"]*)" using the old WebDAV API$/
  • @Then /^the public should be able to download the range "([^"]*)" of file "([^"]*)" from inside the last public shared folder with password "([^"]*)" and the content should be "([^"]*)"$/ -> it uses publicDownloadsTheFileInsideThePublicSharedFolderWithPassword()
@individual-it individual-it self-assigned this Aug 30, 2018
@phil-davis phil-davis changed the title fix steps, so that they really use old/new webdav path fix API acceptance test steps, so that they really use old/new webdav path Sep 24, 2018
@paurakhsharma
Copy link
Member

@individual-it, should we close this now?

@individual-it
Copy link
Member Author

fixed by #33297

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants