mbk-lab
/
nextcloud
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Merge pull request #3404 from nextcloud/fix-welcome.txt 

replace ownCloud with Nextcloud
This commit is contained in:
Morris Jobke 2017-02-08 21:00:58 -06:00 committed by GitHub
parent 3e3021d658 7c53ae3435
commit b2c8e22429
3 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
build/integration/features/dav-v2.feature
View File

@ -14,7 +14,7 @@ Feature: dav-v2
And As an "admin" And As an "admin"
And user "user0" exists And user "user0" exists
And As an "user0" And As an "user0"
When Downloading file "/files/user0/welcome.txt" with range "bytes=51-77" When Downloading file "/files/user0/welcome.txt" with range "bytes=52-78"
Then Downloaded content should be "example file for developers" Then Downloaded content should be "example file for developers"
Scenario: Downloading a file on the new endpoint should serve security headers Scenario: Downloading a file on the new endpoint should serve security headers
@ -30,18 +30,18 @@ Feature: dav-v2
|X-Permitted-Cross-Domain-Policies|none| |X-Permitted-Cross-Domain-Policies|none|
|X-Robots-Tag|none| |X-Robots-Tag|none|
|X-XSS-Protection|1; mode=block| |X-XSS-Protection|1; mode=block|
And Downloaded content should start with "Welcome to your ownCloud account!" And Downloaded content should start with "Welcome to your Nextcloud account!"
Scenario: Doing a GET with a web login should work without CSRF token on the new backend Scenario: Doing a GET with a web login should work without CSRF token on the new backend
Given Logging in using web as "admin" Given Logging in using web as "admin"
When Sending a "GET" to "/remote.php/dav/files/admin/welcome.txt" without requesttoken When Sending a "GET" to "/remote.php/dav/files/admin/welcome.txt" without requesttoken
Then Downloaded content should start with "Welcome to your ownCloud account!" Then Downloaded content should start with "Welcome to your Nextcloud account!"
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
Scenario: Doing a GET with a web login should work with CSRF token on the new backend Scenario: Doing a GET with a web login should work with CSRF token on the new backend
Given Logging in using web as "admin" Given Logging in using web as "admin"
When Sending a "GET" to "/remote.php/dav/files/admin/welcome.txt" with requesttoken When Sending a "GET" to "/remote.php/dav/files/admin/welcome.txt" with requesttoken
Then Downloaded content should start with "Welcome to your ownCloud account!" Then Downloaded content should start with "Welcome to your Nextcloud account!"
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
Scenario: Doing a PROPFIND with a web login should not work without CSRF token on the new backend Scenario: Doing a PROPFIND with a web login should not work without CSRF token on the new backend

14
build/integration/features/webdav-related.feature
View File

@ -12,7 +12,7 @@ Feature: webdav-related
Scenario: download a file with range Scenario: download a file with range
Given using dav path "remote.php/webdav" Given using dav path "remote.php/webdav"
And As an "admin" And As an "admin"
When Downloading file "/welcome.txt" with range "bytes=51-77" When Downloading file "/welcome.txt" with range "bytes=52-78"
Then Downloaded content should be "example file for developers" Then Downloaded content should be "example file for developers"
Scenario: Upload forbidden if quota is 0 Scenario: Upload forbidden if quota is 0
@ -39,7 +39,7 @@ Feature: webdav-related
When user "user0" has a quota of "10 MB" When user "user0" has a quota of "10 MB"
Then as "user0" gets properties of folder "/" with Then as "user0" gets properties of folder "/" with
|{DAV:}quota-available-bytes| |{DAV:}quota-available-bytes|
And the single response should contain a property "{DAV:}quota-available-bytes" with value "10485429" And the single response should contain a property "{DAV:}quota-available-bytes" with value "10485428"
Scenario: Retrieving folder quota of shared folder with quota when no quota is set for recipient Scenario: Retrieving folder quota of shared folder with quota when no quota is set for recipient
Given using dav path "remote.php/webdav" Given using dav path "remote.php/webdav"
@ -57,7 +57,7 @@ Feature: webdav-related
| shareWith | user0 | | shareWith | user0 |
Then as "user0" gets properties of folder "/testquota" with Then as "user0" gets properties of folder "/testquota" with
|{DAV:}quota-available-bytes| |{DAV:}quota-available-bytes|
And the single response should contain a property "{DAV:}quota-available-bytes" with value "10485429" And the single response should contain a property "{DAV:}quota-available-bytes" with value "10485428"
Scenario: Uploading a file as recipient using webdav having quota Scenario: Uploading a file as recipient using webdav having quota
Given using dav path "remote.php/webdav" Given using dav path "remote.php/webdav"
@ -83,7 +83,7 @@ Feature: webdav-related
When creating a share with When creating a share with
| path | welcome.txt | | path | welcome.txt |
| shareType | 3 | | shareType | 3 |
And Downloading last public shared file with range "bytes=51-77" And Downloading last public shared file with range "bytes=52-78"
Then Downloaded content should be "example file for developers" Then Downloaded content should be "example file for developers"
Scenario: download a public shared file inside a folder with range Scenario: download a public shared file inside a folder with range
@ -108,18 +108,18 @@ Feature: webdav-related
|X-Permitted-Cross-Domain-Policies|none| |X-Permitted-Cross-Domain-Policies|none|
|X-Robots-Tag|none| |X-Robots-Tag|none|
|X-XSS-Protection|1; mode=block| |X-XSS-Protection|1; mode=block|
And Downloaded content should start with "Welcome to your ownCloud account!" And Downloaded content should start with "Welcome to your Nextcloud account!"
Scenario: Doing a GET with a web login should work without CSRF token on the old backend Scenario: Doing a GET with a web login should work without CSRF token on the old backend
Given Logging in using web as "admin" Given Logging in using web as "admin"
When Sending a "GET" to "/remote.php/webdav/welcome.txt" without requesttoken When Sending a "GET" to "/remote.php/webdav/welcome.txt" without requesttoken
Then Downloaded content should start with "Welcome to your ownCloud account!" Then Downloaded content should start with "Welcome to your Nextcloud account!"
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
Scenario: Doing a GET with a web login should work with CSRF token on the old backend Scenario: Doing a GET with a web login should work with CSRF token on the old backend
Given Logging in using web as "admin" Given Logging in using web as "admin"
When Sending a "GET" to "/remote.php/webdav/welcome.txt" with requesttoken When Sending a "GET" to "/remote.php/webdav/welcome.txt" with requesttoken
Then Downloaded content should start with "Welcome to your ownCloud account!" Then Downloaded content should start with "Welcome to your Nextcloud account!"
Then the HTTP status code should be "200" Then the HTTP status code should be "200"
Scenario: Doing a PROPFIND with a web login should not work without CSRF token on the old backend Scenario: Doing a PROPFIND with a web login should not work without CSRF token on the old backend

2
core/skeleton/welcome.txt
View File

@ -1,4 +1,4 @@
Welcome to your ownCloud account! Welcome to your Nextcloud account!
This is just an example file for developers and git users. This is just an example file for developers and git users.
The packaged and released versions will come with better examples. The packaged and released versions will come with better examples.