summaryrefslogtreecommitdiffstats
path: root/tests/acceptance
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #34437 from nextcloud/feat/theming-default-system-valueSimon L2022-10-132-3/+3
|\ | | | | Use default system primary
| * Allow to pick custom colourJohn Molakvoæ (skjnldsv)2022-10-132-3/+3
| | | | | | | | Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
* | Make CI green againJoas Schilling2022-10-132-43/+46
|/ | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Use brand color for background only and keep accessible color as color primaryChristopher Ng2022-10-052-2/+23
| | | | Signed-off-by: Christopher Ng <chrng8@gmail.com>
* Fix various theming bugsChristopher Ng2022-09-282-14/+14
| | | | Signed-off-by: Christopher Ng <chrng8@gmail.com>
* Increase timeout for apps managementVincent Petry2022-09-151-1/+1
| | | | Signed-off-by: Vincent Petry <vincent@nextcloud.com>
* Add accessibility entry in user menuVincent Petry2022-09-141-2/+4
| | | | Signed-off-by: Vincent Petry <vincent@nextcloud.com>
* More cleaning up of the login componentCarl Schwan2022-09-061-2/+2
| | | | | | | - Move css in scopped vue components - Port to NcNoteCard all the warning messages Signed-off-by: Carl Schwan <carl@carlschwan.eu>
* Merge pull request #33790 from nextcloud/Valdnet-patch-2Simon L2022-09-022-2/+2
|\ | | | | l10n: Spelling unification
| * fix testsszaimen2022-09-022-2/+2
| | | | | | | | Signed-off-by: szaimen <szaimen@e.mail.de>
* | Maximize browser window before running the testsDaniel Calviño Sánchez2022-09-012-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By the default the browser window is not maximized, but opened with a size of 1050x978px. In the Files app, when the navigation bar and the side bar are both open, with the previous design that width caused the file name to be very very narrow, but still clickable. However, with the updated design the file name is too narrow and no longer clickable, which breaks several acceptance tests that descend into subfolders. To solve that now the browser window is maximized before running the tests, which makes the window wide enough (1360px) to show the file name and make it clickable. This commit also removes a step to close the sidebar that was recently added to address the problem mentioned above in a previous pull request. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Wait for the new user form to be visibleDaniel Calviño Sánchez2022-09-011-2/+6
| | | | | | | | | | | | | | | | | | | | | | Before it was checked if the new user form was visible, but it was not waited for it. It seems that it can happen that the new user form is in the DOM, and therefore found, but not visible yet when the tests run, which caused them to (randomly) fail. Due to that now it is explicitly waited until it is visible, rather than assuming that it is visible as soon as it appears in the DOM. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Adjust theming acceptance testsJulius Härtl2022-09-012-10/+10
|/ | | | Signed-off-by: Julius Härtl <jus@bitgrid.net>
* Merge pull request #33756 from nextcloud/enh/noid/admin-settings-directlySimon L2022-08-317-16/+25
|\ | | | | add a way to open the admin settings overview directly
| * fix testsszaimen2022-08-317-16/+25
| | | | | | | | | | Signed-off-by: szaimen <szaimen@e.mail.de> Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Adjust acceptance tests to changes in app menuDaniel Calviño Sánchez2022-08-311-2/+2
|/ | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Adjust acceptance test selectorsVincent Petry2022-08-255-7/+8
| | | | Signed-off-by: Vincent Petry <vincent@nextcloud.com>
* Fix integration testsCarl Schwan2022-08-011-2/+2
| | | | | | | The html tags changed in the notification apps, adapt selector to the new state Signed-off-by: Carl Schwan <carl@carlschwan.eu>
* Redesign guest pages for better accessibilityCarl Schwan2022-07-271-18/+6
| | | | | | | - Use white box and put content on it - Improve focus indicator Signed-off-by: Carl Schwan <carl@carlschwan.eu>
* Adjust acceptance tests to changes in sharing tabDaniel Calviño Sánchez2022-07-261-1/+1
| | | | | | | The name of the user shared with is now marked with a "span" rather than with "h5". Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Replace files app ids to classesVincent Petry2022-07-261-3/+3
| | | | | | | | | | | Replaced ids to classes for the following: - #filestable -> .files-filestable - #fileList -> .files-fileList - #controls -> .files-controls - #emptycontent -> .emptyfilelist.emptycontent Signed-off-by: Vincent Petry <vincent@nextcloud.com>
* Update dependencies in acceptance tests composer.lockCôme Chilliet2022-06-131-327/+899
| | | | | | It should allow to run them on PHP>=8.0 with a recent phpunit. Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
* More meaningfull message when a public authenticated share's password is ↵Cyrille Bollu2022-05-311-1/+1
| | | | | | wrong or has expired Signed-off-by: Cyrille Bollu <cyrpub@bollu.be>
* Require a recent phpunit version in integration and acceptanceCôme Chilliet2022-05-243-260/+708
| | | | | | Otherwise build with PHP>8 will fail as PHPUnit 6 does not support it Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
* Adjust acceptance tests to changes in notifications markupDaniel Calviño Sánchez2022-05-031-1/+1
| | | | | | | Since nextcloud/notifications#1178 each notification in the list is a "<li>" rather than a "<div>". Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Fix acceptanceJohn Molakvoæ2022-04-211-1/+1
| | | | Signed-off-by: John Molakvoæ <skjnldsv@protonmail.com>
* Update images in scripts to run local tests in DockerDaniel Calviño Sánchez2022-03-031-1/+1
| | | | | | | | PHP 7.3 support was dropped for Nextcloud 24. The Docker images are updated to the same images used for integration and acceptance tests in CI. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Profile backendChristopher Ng2021-10-191-2/+2
| | | | Signed-off-by: Christopher Ng <chrng8@gmail.com>
* Merge pull request #29064 from ↵Louis2021-10-061-1/+7
|\ | | | | | | | | nextcloud/feature/add_cache_to_local_integration_tests_container Add caching for local run of integration and acceptance tests
| * Add cache for local integration test containerLouis Chemineau2021-10-061-1/+7
| | | | | | | | Signed-off-by: Louis Chemineau <louis@chmn.me>
* | Fix app-files acceptance testsLouis Chemineau2021-10-061-2/+2
|/ | | | Signed-off-by: Louis Chemineau <louis@chmn.me>
* Bump @nextcloud/vueJohn Molakvoæ2021-09-162-3/+3
| | | | Signed-off-by: John Molakvoæ <skjnldsv@protonmail.com>
* Handle single action unshareJulius Härtl2021-06-091-4/+16
| | | | Signed-off-by: Julius Härtl <jus@bitgrid.net>
* Settings: new user row replaced by a modalSimounet2021-04-211-1/+1
| | | | Signed-off-by: Simounet <contact@simounet.net>
* Add automatic handling of "ElementNotInteractable" exceptionsDaniel Calviño Sánchez2021-04-191-1/+24
| | | | | | | | | | | | | | | | | | | | | | | In the WebDriver protocol, when a command fails because it can not interact with the target element, an "element not interactable" error is generated. It can be a transitive issue (for example, due to an animation), so when the error is received the command should be tried again, just like done, for example, with "ElementNotVisible" exceptions. However, the last version of the "instaclick/php-webdriver" library compatible with the Selenium Driver of Mink did not support yet that WebDriver error. And even if Chrome is run using the old protocol an unknown "element not interactable" error can be received anyway in some cases. When an unknown error is received by the "instaclick/php-webdriver" library it is thrown as a generic Exception so, until the library can be updated, the message of generic exceptions is checked and the command is retried if it matched. For the time being "element not interactable" errors are handled like "ElementNotVisible" exceptions; this may need to change once the error is better understood. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Update acceptance tests to Selenium 3Daniel Calviño Sánchez2021-04-162-2/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The acceptance tests used the last Selenium 2 Docker container available, which provides a rather old Firefox version (Firefox 47). Nevertheless, despite some rendering issues, most things still worked as expected due to the JavaScript files being built with support for older browsers. However, now that support for Internet Explorer 11 and older browsers will be dropped things could start to fail, so a newer browser (and thus a newer Selenium version) should be used in the acceptance tests. Selenium has been standardized by the W3C, and the protocol to communicate between the Selenium server and the browser has changed due to that. Firefox >= 48 only supports the new W3C protocol, but the Selenium driver for Mink does not support it yet. The old protocol can still be used in recent Chromium/Chrome versions by explicitly forcing it, so for the time being the acceptance tests will need to be run on Chrome instead (although Firefox provides some interesting features like the fake streams that would be needed to test calls in Talk, so they should be moved again to Firefox once possible). Finally, the default shm size of Docker is 64 MiB. This does not seem enough to run newer Chrome releases and causes the browser to randomly crash during the tests ("unknown error: session deleted because of page crash" is shown in the logs). Due to this "disable-dev-shm-usage" needs to be used so Chrome writes shared memory files into "/tmp" instead of "/dev/shm" (the default shm size of Docker could have been increased instead using "docker run --shm-size...", but that seems to be problematic when the container is run in current Drone releases). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Replace carriage return with WebDriver "ENTER" constantDaniel Calviño Sánchez2021-04-162-2/+4
| | | | | | | | | | When the value is set in some input fields a carriage return was sent to simulate pressing the enter key and thus confirming the input. However, different browsers use different keys (Firefox uses "\r", but Chrome uses "\n"), so the carriage return was replaced with the WebDriver "ENTER" constant which is common to both browsers. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Do not send "enter" key when not neededDaniel Calviño Sánchez2021-04-163-3/+3
| | | | | | | | | Sending the "enter" key is not needed in those input fields that auto save while the user is typing or when the focus is lost (which since version 1.4.0 the Selenium driver for Mink is automatically done after setting the value). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Update Mink from 1.7.1 to 1.8.1 in acceptance testsDaniel Calviño Sánchez2021-03-303-17/+24
| | | | | | | | Since version 1.8.0 of Mink "Mink::getSession()" no longer starts the session automatically (see https://github.com/minkphp/Mink/pull/705), so it now needs to be explicitly started. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Update Selenium driver for Mink from 1.3.1 to 1.4.0 in acceptance testsDaniel Calviño Sánchez2021-03-304-20/+30
| | | | | | | | | | | | | | | | | | | | | | | | Since version 1.4.0 the Selenium driver for Mink uses again the element on which the value was set (see https://github.com/minkphp/MinkSelenium2Driver/pull/286). When creating a new folder or renaming one sending a new line ("\r") caused the element on which the value was set to be removed, so the element was no longer attached to the DOM when the driver tried to use it again, and thus a "StaleElementReference" exception was thrown. Due to this now it is needed to explicitly click the confirm button when creating a new folder. In the case of the renaming, on the other hand, nothing else besides not sending the new line is needed, as the Selenium driver now unfocuses the element (that is why it uses again the element after setting the value) which triggers the renaming. Besides that, the Selenium driver for Mink uses a library to simulate certain events, bitovi/syn. In version 1.4.0 that library was updated to version 0.0.3, which seems to somehow break pressing the "escape" key. Due to this now the sharing menu has to be closed by pressing "enter" on the share menu button instead. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Update Behat from 3.7.0 to 3.8.1 in acceptance testsDaniel Calviño Sánchez2021-03-302-18/+18
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Update PHPUnit from 4.X to 6.X in acceptance testsDaniel Calviño Sánchez2021-03-3020-268/+682
| | | | | | | | The PHPUnit update also required an update of "symfony/yaml", so besides the changes needed for PHPUnit the "behat.yml" file also had to be adjusted. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Change label also in the acceptance testsJoas Schilling2021-03-101-4/+4
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Merge pull request #25990 from ↵kesselb2021-03-081-7/+3
|\ | | | | | | | | nextcloud/do-not-try-to-add-an-existing-user-again-in-acceptance-tests Do not try to add an existing user again in acceptance tests
| * Remove unneeded steps to add already existing userDaniel Calviño Sánchez2021-03-071-5/+0
| | | | | | | | | | | | | | User "user1" is added when installing and configuring the server, so it is already added in all tests. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Fix acceptance test for searching just added users in contacts menuDaniel Calviño Sánchez2021-03-071-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | User "user1" is added when installing and configuring the server, so it is already added in all tests. As the test verifies that just added users can be searched in the contacts menu a new user should be actually added. The test did not fail because it assumed that "user1" did not exist and just checked that it existed after "adding" it, but not whether adding it failed. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Find directly the label instead of falling back to itDaniel Calviño Sánchez2021-03-061-8/+1
| | | | | | | | | | | | | | | | The input element is always hidden, so the check always ended falling back to the label. Moreover, the label is the element that the user interacts with, so it must be the one used. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Assert also element visibility instead of just finding itDaniel Calviño Sánchez2021-03-061-4/+12
| | | | | | | | | | | | | | | | Although if the element could not be found an exception would be thrown and the test aborted if an element is in the DOM but hidden it would be found and the test would pass. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Add explicit locator for "Enable all" bundle buttonDaniel Calviño Sánchez2021-03-061-5/+7
| | | | | | | | | | | | | | | | | | | | | | Instead of looking for the bundle button and then checking its value now the expected value is included in the locator and the button is checked similarly to other elements. No "Disable all" locator was added as it was not currently needed anywhere. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Find elements through the actor rather than the driverDaniel Calviño Sánchez2021-03-061-4/+30
| | | | | | | | | | | | | | | | | | | | "Actor::find" is a more robust way to look for elements, as it handles some exceptions that may be thrown. Therefore, even if the elements are not actually used and it is only checked whether they exist or not using the actor is the preferred way when possible (and it also makes it consistent with the rest of the acceptance tests). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-15 11:00:37 +0000