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

[tests-only]Added tests for folder creation and syncing (part 2) #9258

Merged
merged 1 commit into from
Dec 15, 2021
Merged
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
37 changes: 36 additions & 1 deletion test/gui/tst_syncing/test.feature
Original file line number Diff line number Diff line change
Expand Up @@ -245,7 +245,7 @@ Feature: Syncing files
And as "Alice" folder "Folder1/subFolder1/subFolder2" should exist on the server

@skip @issue-9281
Scenario: Filenames that are rejected by the server are reported
Scenario: Filenames that are rejected by the server are reported
Given user "Alice" has set up a client with default settings
And user "Alice" has created a folder "Folder1" inside the sync folder
When user "Alice" creates a file "Folder1/a\\a.txt" with the following content inside the sync folder
Expand All @@ -257,3 +257,38 @@ Feature: Syncing files
When the user clicks on the activity tab
And the user selects "Not Synced" tab in the activity
Then the file "Folder1/a\\a.txt" should be blacklisted


Scenario Outline: Verify one empty folder with a length longer than the allowed limit will not be synced
Given user "Alice" has set up a client with default settings
And user "Alice" has created a folder "<foldername>" inside the sync folder
When user "Alice" creates a folder "<foldername>/<foldername>" inside the sync folder
And user "Alice" creates a folder "<foldername>/<foldername>/<foldername>" inside the sync folder
And user "Alice" creates a folder "<foldername>/<foldername>/<foldername>/<foldername>" inside the sync folder
And user "Alice" creates a folder "<foldername>/<foldername>/<foldername>/<foldername>/<foldername>" inside the sync folder
And the user waits for folder "<foldername>/<foldername>/<foldername>/<foldername>/<foldername>" to be synced
Then as "Alice" folder "<foldername>" should exist on the server
And as "Alice" folder "<foldername>/<foldername>" should exist on the server
And as "Alice" folder "<foldername>/<foldername>/<foldername>" should exist on the server
And as "Alice" folder "<foldername>/<foldername>/<foldername>/<foldername>" should exist on the server
And as "Alice" folder "<foldername>/<foldername>/<foldername>/<foldername>/<foldername>" should exist on the server
Examples:
| foldername |
| An empty folder which name is obviously more than 59 characters |


Scenario: Invalid system names are synced in linux
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can remove this scenario if we include it in the scenarios Syncing a file to the server and Syncing a folder to the server

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is better this way.

Given user "Alice" has set up a client with default settings
And user "Alice" has created folder "COM" on the server
And user "Alice" has created folder "test%" on the server
And user "Alice" has uploaded file on the server with content "server content" to "/PRN"
And user "Alice" has uploaded file on the server with content "server content" to "/foo%"
When the user waits for the files to sync
Then the folder "COM" should exist on the file system
And the folder "test%" should exist on the file system
And the file "PRN" should exist on the file system
And the file "foo%" should exist on the file system
And as "Alice" folder "COM" should exist on the server
And as "Alice" folder "test%" should exist on the server
And as "Alice" file "/PRN" should exist on the server
And as "Alice" file "/foo%" should exist on the server