summaryrefslogtreecommitdiffstats
path: root/tests/acceptance
Commit message (Collapse)AuthorAgeFilesLines
* fix the folder shareGretaD2019-12-191-4/+4
| | | | | Signed-off-by: GretaD <gretadoci@gmail.com> Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>
* Move users management to multi lineGreta Doci2019-12-122-36/+73
| | | | Signed-off-by: Greta Doci <gretadoci@gmail.com>
* Adjust tags acceptance tests to moved admin sectionJulius Härtl2019-11-281-3/+3
| | | | Signed-off-by: Julius Härtl <jus@bitgrid.net>
* Make phpunit8 compatibleRoeland Jago Douma2019-11-272-2/+2
| | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Accept incoming shares in acceptance testsDaniel Calviño Sánchez2019-11-205-18/+128
| | | | | | | | | | | | | | | | | Incoming shares are no longer automatically added to the file list of the sharee. Instead, the user now needs to explictly accept the share. Currently shares can be accepted only from the Notifications app, so it must be explicitly cloned before installing Nextcloud if it is not found in the "apps" directory. Note that the development branches are already built, so there is no need to explicitly build the app. With the new sharing behaviour the "share a skeleton file with another user before first login" scenario is no longer valid (as the user will need to log in to accept the share, so at that point the skeleton is already created), so it was removed. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Rename "Notification" to "Toast"Daniel Calviño Sánchez2019-11-202-11/+11
| | | | | | | | Since Nextcloud 17 the proper name for the old built-in notifications is "Toast". Moreover, this will reduce ambiguity when using the "notification" term to refer to elements in the Notifications app. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Adjust acceptance tests to new OCA.SidebarJohn Molakvoæ (skjnldsv)2019-10-294-46/+53
| | | | Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
* Run acceptance tests on PHP 7.3Daniel Calviño Sánchez2019-10-221-1/+1
| | | | | | | | There is no difference (as far as I know) between running the acceptance tests on PHP 7.1 or on PHP 7.3; this is simply a preparatory step to be ready when PHP 7.1 support is dropped in Nextcloud server. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Fix tag acceptance tests after #16682John Molakvoæ (skjnldsv)2019-10-042-3/+19
| | | | Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
* Remove input id on login formJohn Molakvoæ (skjnldsv)2019-09-281-1/+1
| | | | | Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com> Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>
* Adjust acceptance tests to changes in link share menu behaviourGreta Doci2019-08-291-8/+0
| | | | | | | | | | | | | | | | Now the link share menu is not automatically opened after a link share is created, so waiting until it was opened failed in iShareTheLinkFor. Note that the steps that interact with the link share menu take care themselves of showing the menu if needed, so there is no need to explicitly show it despite the change. Also, the waiting in iShareTheLinkFor was introduced when the link share menu was changed to automatically open after creating a link share, as that caused some issues with the steps that opened the menu by themselves (fec8d12fc5). Due to all this, now that the link share menu is again not automatically opened the wait can be simply removed. Signed-off-by: Greta Doci <gretadoci@gmail.com>
* Allow Context subclasses in acceptance tests to access parent actorDaniel Calviño Sánchez2019-08-161-1/+1
| | | | | | | | | | Although uncommon, in some cases a Context may need to be extended (for example, to override a step defined in the server with a specific behaviour in the acceptance tests of an app); in those cases the subclass should be able to access the actor attribute defined in the Context it is extending. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Adjust acceptance tests to notifications based on toastify (#15938)John Molakvoæ2019-06-131-2/+2
|\ | | | | Adjust acceptance tests to notifications based on toastify
| * Adjust acceptance tests to notifications based on toastifyDaniel Calviño Sánchez2019-06-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | The old notifications were added as ".row" elements to the "#notification-container" element; the new notifications based on toastify are added as ".toastify .on .toast..." elements to the "#content" element. Besides that, they also include a span element with an X to close the notification, so now only the first child text node should be compared to the expected message. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Add messages to assertFalse/True to clarify the failed assertionDaniel Calviño Sánchez2019-06-121-3/+6
|/ | | | | | | | Otherwise the output would just read "Failed asserting that true is false." or "Failed asserting that false is true.", which is not very informative when there are several assertFalse/True in a row. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Disable acceptance test which should fail anywayJoas Schilling2019-04-111-8/+9
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Add acceptance test for public folder navigationJulius Härtl2019-04-101-0/+20
| | | | Signed-off-by: Julius Härtl <jus@bitgrid.net>
* Adjust acceptance tests to changes of file names in file pickerDaniel Calviño Sánchez2019-04-031-1/+3
| | | | | | | | | File names are no longer shown directly in the ".filename" element, but split in two "span" elements inside a ".filename-parts" element, so now the texts in those span elements need to be concatenated to get the file name. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Revert "Temp disable bundle tests"Roeland Jago Douma2019-04-011-8/+8
|
* Temp disable bundle testsRoeland Jago Douma2019-03-201-8/+8
| | | | | | | | | | | | The bundle acceptance tests fails after #14578 sometimes. This is because of a race condition. not all apps have compatible 16 versions yet. So trying to enable them results in those apps doing :boom:. Because of #14578 we do show them now. So we try to enable them. However depending on which requests finishes first the disable button for the audit app either shows up or now. Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Improve startup speed of acceptance testsJoas Schilling2019-03-181-1/+12
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Adjust acceptance testsMorris Jobke2019-03-182-1/+20
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing files app test - act 4Morris Jobke2019-03-141-6/+6
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing files app test - act 3Morris Jobke2019-03-141-20/+20
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing app management testMorris Jobke2019-03-141-16/+16
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing comments app test - act 2Morris Jobke2019-03-141-6/+6
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing files app test - act 2Morris Jobke2019-03-141-10/+10
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable fragile user acceptance testsMorris Jobke2019-03-131-18/+18
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing login testMorris Jobke2019-03-131-10/+10
| | | | | | | | | | | | | | | | | | | | | | | * tests/acceptance/features/login.feature:15 <details><summary>Show full log</summary> ``` Scenario: log in with valid user and invalid password once fixed by admin # /drone/src/github.com/nextcloud/server/tests/acceptance/features/login.feature:15 Given I act as John # ActorContext::iActAs() And I can not log in with user user0 and password 654231 # LoginPageContext::iCanNotLogInWithUserAndPassword() When I act as Jane # ActorContext::iActAs() And I am logged in as the admin # LoginPageContext::iAmLoggedInAsTheAdmin() And I open the User settings # SettingsMenuContext::iOpenTheUserSettings() And I set the password for user0 to 654321 # UsersSettingsContext::iSetTheFieldForUserTo() And I act as John # ActorContext::iActAs() And I log in with user user0 and password 654321 # LoginPageContext::iLogInWithUserAndPassword() Then I see that the current page is the Files app # FilesAppContext::iSeeThatTheCurrentPageIsTheFilesApp() Failed asserting that 'http://acceptance-login/index.php/login?user=user0' starts with "http://acceptance-login/index.php/apps/files/". ``` </details> Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing comments testMorris Jobke2019-03-131-8/+8
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing files app testMorris Jobke2019-03-131-114/+114
| | | | | | | | | | | | | | | | | | | | Fails with: * tests/acceptance/features/app-files.feature:90 <details><summary>Show full log</summary> ``` Scenario: show favorites # /drone/src/github.com/nextcloud/server/tests/acceptance/features/app-files.feature:90 Given I am logged in # LoginPageContext::iAmLoggedIn() And I mark "welcome.txt" as favorite # FileListContext::iMarkAsFavorite() When I open the "Favorites" section # AppNavigationContext::iOpenTheSection() Then I see that the current section is "Favorites" # AppNavigationContext::iSeeThatTheCurrentSectionIs() Then I see that the file list contains a file named "welcome.txt" # FileListContext::iSeeThatTheFileListContainsAFileNamed() Row for file welcome.txt in file list could not be found after 100 seconds (NoSuchElementException) ``` </details> Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing apps management testMorris Jobke2019-03-131-3/+3
| | | | | | | | | | | | | | | | | | | | | | | Fails with: * tests/acceptance/features/apps.feature:66 <details><summary>Show full log</summary> ``` Scenario: Show section from app store # /drone/src/github.com/nextcloud/server/tests/acceptance/features/apps.feature:66 Given I act as Jane # ActorContext::iActAs() And I am logged in as the admin # LoginPageContext::iAmLoggedInAsTheAdmin() And I open the Apps management # SettingsMenuContext::iOpenTheAppsManagement() And I see that the current section is "Your apps" # AppNavigationContext::iSeeThatTheCurrentSectionIs() When I open the "Files" section # AppNavigationContext::iOpenTheSection() Files section item in App Navigation could not be found after 100 seconds (NoSuchElementException) Then I see that there some apps listed from the app store # AppsManagementContext::iSeeThatThereSomeAppsListedFromTheAppStore() And I see that the current section is "Files" # AppNavigationContext::iSeeThatTheCurrentSectionIs() ``` </details> Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable failing files tag testMorris Jobke2019-03-131-76/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fails with: * tests/acceptance/features/app-files-tags.feature:42 <details><summary>Show full log</summary> ``` Scenario: add tags using the dropdown in the details view # /drone/src/github.com/nextcloud/server/tests/acceptance/features/app-files-tags.feature:42 Given I am logged in as the admin # LoginPageContext::iAmLoggedInAsTheAdmin() And I visit the settings page # SettingsMenuContext::iVisitTheSettingsPage() And I open the "Tag management" section # AppNavigationContext::iOpenTheSection() And I see that the button to select tags is shown # SettingsContext::iSeeThatTheButtonToSelectTagsIsShown() And I create the tag "tag1" in the settings # SettingsContext::iCreateTheTagInTheSettings() And I create the tag "tag2" in the settings # SettingsContext::iCreateTheTagInTheSettings() And I create the tag "tag3" in the settings # SettingsContext::iCreateTheTagInTheSettings() And I create the tag "tag4" in the settings # SettingsContext::iCreateTheTagInTheSettings() And I see that the dropdown for tags in the settings eventually contains the tag "tag1" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag() And I see that the dropdown for tags in the settings eventually contains the tag "tag2" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag() And I see that the dropdown for tags in the settings eventually contains the tag "tag3" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag() And I see that the dropdown for tags in the settings eventually contains the tag "tag4" # SettingsContext::iSeeThatTheDropdownForTagsInTheSettingsEventuallyContainsTheTag() And I log out # SettingsMenuContext::iLogOut() And I am logged in # LoginPageContext::iAmLoggedIn() And I open the details view for "welcome.txt" # FileListContext::iOpenTheDetailsViewFor() And I open the input field for tags in the details view # FilesAppContext::iOpenTheInputFieldForTagsInTheDetailsView() When I check the tag "tag2" in the dropdown for tags in the details view # FilesAppContext::iCheckTheTagInTheDropdownForTagsInTheDetailsView() And I check the tag "tag4" in the dropdown for tags in the details view # FilesAppContext::iCheckTheTagInTheDropdownForTagsInTheDetailsView() Then I see that the tag "tag2" in the dropdown for tags in the details view is checked # FilesAppContext::iSeeThatTheTagInTheDropdownForTagsInTheDetailsViewIsChecked() And I see that the tag "tag4" in the dropdown for tags in the details view is checked # FilesAppContext::iSeeThatTheTagInTheDropdownForTagsInTheDetailsViewIsChecked() And I see that the input field for tags in the details view contains the tag "tag2" # FilesAppContext::iSeeThatTheInputFieldForTagsInTheDetailsViewContainsTheTag() Failed asserting that false is true. And I see that the input field for tags in the details view contains the tag "tag4" # FilesAppContext::iSeeThatTheInputFieldForTagsInTheDetailsViewContainsTheTag() ``` </details> Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Fix acceptance tests for wrong password message due to changed messageMorris Jobke2019-03-111-1/+1
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Disable fragile tests for nowMorris Jobke2019-03-053-16/+16
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Make header.feature more robust by running it on apacheMorris Jobke2019-03-041-0/+1
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Run tests that fail with "no such process" over to apache serverMorris Jobke2019-02-284-0/+4
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Fix acceptance tests for tag managementMorris Jobke2019-02-281-3/+3
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Add acceptance tests for copying files to the same folderDaniel Calviño Sánchez2019-01-221-0/+33
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Add acceptance tests for moving and copying selections to another folderDaniel Calviño Sánchez2019-01-222-0/+126
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Add acceptance tests for moving and copying files to another folderDaniel Calviño Sánchez2019-01-224-0/+178
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Add acceptance tests for opening search results for commentsDaniel Calviño Sánchez2018-12-213-0/+91
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Add acceptance tests for searching commentsDaniel Calviño Sánchez2018-12-213-0/+152
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Add acceptance tests for comments on shared files and foldersDaniel Calviño Sánchez2018-12-062-0/+209
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Merge pull request #12649 from ↵Morris Jobke2018-11-262-2/+7
|\ | | | | | | | | nextcloud/make-acceptance-tests-for-comments-more-robust Make acceptance tests for comments more robust
| * Wait for the comment to be added before changing to another fileDaniel Calviño Sánchez2018-11-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the server is too slow, changing to a different file immediately after sending a new comment but without waiting for the comment to be shown for the original file could cause the new comment to be shown for the current file instead. This is, indeed, a bug in the comments. However, it is not possible to test it reliably in the acceptance tests, as it depends on how fast the server adds the message and how fast the client changes to a different file; sometimes the test would fail and sometimes it would not. Therefore, now it is waited for the comment to be added before changing to another file, as in this case it can be reliably tested that changing to a different file does not cause the comments from the previous file to be shown in the current file (this was a different bug already fixed and due to which this test was added in the first place). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Wait for the empty content element to be shownDaniel Calviño Sánchez2018-11-241-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | When the "Comments" tab is open the empty content element is always in the DOM, although it is only shown once the message collection was fetched and there were no messages. Due to this it is necessary to explicitly wait for it to be shown instead of relying on the implicit wait made to find the element; otherwise it would be found immediately and if the collection was not fetched yet it would not be visible, causing the test to fail. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Rename "FilesSharingAppContext" to "PublicShareContext"Daniel Calviño Sánchez2018-11-232-3/+3
| | | | | | | | | | | | | | | | Having both "FilesAppSharingContext" and "FilesSharingAppContext" was confusing, so "FilesSharingAppContext" was renamed to a more descriptive name. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Extract locators and steps for sharing in Files app to their own contextDaniel Calviño Sánchez2018-11-233-489/+519
| | | | | | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Extract sharing related acceptance tests to their own feature filesDaniel Calviño Sánchez2018-11-233-416/+418
| | | | | | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-01 09:20:30 +0000