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

[full-ci] [tests-only] Removed core bug demonstration scenarios #5489

Merged
merged 1 commit into from
Feb 1, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -536,7 +536,7 @@ Feature: share resources where the sharee receives the share in multiple ways
| path |
| /child1 |

@skipOnOcV10 @issue-39347

Scenario Outline: Share receiver renames the received group share and shares same folder through user share again
Given using OCS API version "<ocs_api_version>"
And group "grp" has been created
Expand Down Expand Up @@ -567,7 +567,7 @@ Feature: share resources where the sharee receives the share in multiple ways
| 1 | 100 |
| 2 | 200 |

@skipOnOcV10 @issue-39347

Scenario Outline: Share receiver renames a group share and receives same resource through user share with additional permissions
Given using OCS API version "<ocs_api_version>"
And group "grp" has been created
Expand Down Expand Up @@ -596,7 +596,7 @@ Feature: share resources where the sharee receives the share in multiple ways
| 1 |
| 2 |

@skipOnOcV10 @issue-39347

Scenario Outline: Share receiver renames a group share and receives same resource through user share with less permissions
Given using OCS API version "<ocs_api_version>"
And group "grp" has been created
Expand Down

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -587,7 +587,7 @@ Feature: create a public link share
| old |
| new |

@issue-37605 @skipOnOcV10

Scenario: Get the mtime of a file inside a folder shared by public link using new webDAV version
Given user "Alice" has created folder "testFolder"
And user "Alice" has created a public link share with settings
Expand All @@ -599,7 +599,7 @@ Feature: create a public link share
And as "Alice" the mtime of the file "testFolder/file.txt" should be "Thu, 08 Aug 2019 04:18:13 GMT"
And the mtime of file "file.txt" in the last shared public link using the WebDAV API should be "Thu, 08 Aug 2019 04:18:13 GMT"

@issue-37605 @skipOnOcV10

Scenario: overwriting a file changes its mtime (new public webDAV API)
Given user "Alice" has created folder "testFolder"
When user "Alice" uploads file with content "uploaded content for file name ending with a dot" to "testFolder/file.txt" using the WebDAV API
Expand Down

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Feature: copying from public link share
And as "Alice" file "/PARENT/copy1.txt" should exist
And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data 0"

@skipOnOcV10 @issue-ocis-reva-373 @issue-37683
@issue-ocis-reva-373
Scenario: Copy folder within a public link folder to the same folder name as an already existing file
Given user "Alice" has created folder "/PARENT/testFolder"
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
Expand All @@ -85,7 +85,7 @@ Feature: copying from public link share
Then the HTTP status code should be "204"
And as "Alice" file "/PARENT/copy1.txt" should not exist

@skipOnOcV10 @issue-ocis-reva-373 @issue-37683
@issue-ocis-reva-373
Scenario: Copy file within a public link folder to a file with name same as an existing folder
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
And user "Alice" has created folder "/PARENT/new-folder"
Expand Down

This file was deleted.

Loading