summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Automatic injection into the FetchersJoas Schilling2017-05-103-3/+18
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Automatic creation of Identity managerJoas Schilling2017-05-101-3/+14
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Automatic injection for CssControllerJoas Schilling2017-05-101-3/+10
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Automatic injection for JsControllerJoas Schilling2017-05-101-1/+9
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Merge pull request #4718 from ↵Morris Jobke2017-05-083-78/+493
|\ | | | | | | | | nextcloud/handle-stalled-or-invisible-elements-automatically-in-acceptance-tests Handle stale or invisible elements automatically in acceptance tests
| * Add automatic handling of common command failures of Mink elementsDaniel Calviño Sánchez2017-05-063-2/+315
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commands executed on Mink elements may fail for several reasons. ElementWrapper is introduced to automatically handle some of those situations, like StaleElementReference exceptions and ElementNotVisible exceptions. StaleElementReference exceptions are thrown when the command is executed on an element that is no longer attached to the DOM. When that happens the ElementWrapper finds again the element and executes the command again on the new element. ElementNotVisible exceptions are thrown when the command requires the element to be visible but the element is not. When that happens the ElementWrapper waits for the element to be visible before executing the command again. These changes are totally compatible with the current acceptance tests. They just make the tests more robust, but they do not change their behaviour. In fact, this should minimize some of the sporadic failures in the acceptance tests caused by their concurrent nature with respect to the web browser executing the commands. However, the ElementWrapper is not a silver bullet; it handles the most common situations, but it does not handle every possible scenario. For example, the acceptance tests would still fail sporadically if an element can become staled several times in a row (uncommon) or if it does not become visible before the timeout expires (which could still happen in a loaded system even if the components under test work right, but obviously it is not possible to wait indefinitely for them). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Extract element finding to a command objectDaniel Calviño Sánchez2017-05-062-78/+178
| | | | | | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Make internal find methods staticDaniel Calviño Sánchez2017-05-061-8/+10
| | | | | | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Add missing type hintsDaniel Calviño Sánchez2017-05-061-3/+3
| | | | | | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Increase device password entropy. Use lower- and upper-case characters and ↵Fabrizio Steiner2017-05-081-3/+3
|/ | | | | | digits, but exclude ambiguous characters. The number of digits has also been increased to 25. Signed-off-by: Fabrizio Steiner <fabrizio.steiner@gmail.com>
* Make cache tests a bit more clearMorris Jobke2017-05-042-12/+44
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Update login flow redirectionMario Danic2017-05-041-2/+2
| | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* Merge pull request #4682 from ↵Morris Jobke2017-05-044-11/+96
|\ | | | | | | | | nextcloud/try-to-start-browser-sessions-again-when-they-fail-in-acceptance-tests Try to start browser sessions again when they fail in acceptance tests
| * Add option to acceptance test runners to set a custom timeout multiplierDaniel Calviño Sánchez2017-05-032-1/+48
| | | | | | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Try again to start browser sessions when they failDaniel Calviño Sánchez2017-05-031-1/+27
| | | | | | | | | | | | | | | | | | Starting a session for an Actor can fail, typically, due to a timeout connecting with the web browser. Now if the session fails to start it will be tried again up to "actorTimeoutMultiplier" times in total before giving up. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Generalize attribute nameDaniel Calviño Sánchez2017-05-031-8/+8
| | | | | | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * Fix exponential increase of timeout when finding ancestor elementsDaniel Calviño Sánchez2017-05-031-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | The timeout passed to the "find" method was multiplied by the "findTimeoutMultiplier" attribute. However, as "find" used "findAncestor" and "findAncestor", in turn, used "find" itself the timeout was increased exponentially for ancestor elements. Now "find" was split in "find" and "findInternal"; the first method is the public one and modifies the given parameters as needed and then calls the second method, private, that performs the find itself. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Merge pull request #4662 from ↵Morris Jobke2017-05-026-30/+33
|\ \ | | | | | | | | | | | | nextcloud/remove-named-selectors-from-acceptance-tests Remove named selectors from acceptance tests
| * | Replace "named" Mink selectors with "named_exact" Mink selectorsDaniel Calviño Sánchez2017-05-021-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "named" Mink selector first tries to find an exact match for its locator and then, if not found, tries to find a partial match. Besides other harder to track problems (see comment in the commit in which the "content" locator was removed), this could cause, for example, finding an action link titled "Favorited" when looking for the action link titled "Favorite" (that is, one that conveys the opposite state to the one found). Although currently all the acceptance tests are compatible with both the "named" and the "named_exact" Mink selectors the predefined locators are modified to use the "named_exact" Mink selector to make them more future-proof; the "named" Mink selector can still be used if needed through the "customSelector" method in the builder object. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
| * | Remove "content" locator from acceptance testsDaniel Calviño Sánchez2017-05-026-16/+19
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "content" locator uses the "named" Mink selector and the "content" Mink locator to find the element. The "named" Mink first tries to find the elements whose content match exactly the given content but, if none is found, then it tries to find elements that just contain the given content. This behaviour can lead to hard to track issues. Finding the exact match and, if not found, finding the partial match is done in quick succession. In most cases, when looking for an exact match the element is already there, it is returned, and everything works as expected. Or it may not be there, but then it is not there either when finding the partial match, so no element is returned, and everything works as expected (that is, the actor tries to find again the element after some time). However, it can also happen that when looking for an exact match there is no element yet, but it appears after trying to find the exact match but before trying to find the partial match. In that situation the desired element would be returned along with its ancestors. However, as only the first found element is taken into account and the ancestors would appear first the find action would be successful, but the returned element would not be the expected one. This is highly unlikely, yet possible, and can cause sporadic failures in acceptance tests that, apparently, work as expected. Using a "named_exact" Mink selector instead of the "named" Mink selector does not provide the desired behaviour in most cases either. As it finds any element whose content matches exactly the given content, looking for "Hello world" in "<div><p><a>Hello world</a></p></div>" would match the "div", "p" and "a" elements; in that situation the "div" element would be the one returned, when typically the "a" element would be the expected one. As it is error prone and easily replaceable by more robust locators the "content" locator was removed from the predefined ones (although it can still be used if needed through the "customSelector" method in the builder object). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Merge pull request #4665 from nextcloud/enable-redisMorris Jobke2017-05-021-0/+12
|\ \ | | | | | | Add redis support to our CI jobs
| * | Add redis support to our CI jobsMorris Jobke2017-05-021-0/+12
| | | | | | | | | | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* | | Merge pull request #4620 from nextcloud/preview-error-handlingRoeland Jago Douma2017-05-021-0/+3
|\ \ \ | | | | | | | | better handling of preview generation errors
| * | | fix preview testsRobin Appelman2017-05-021-0/+3
| | | | | | | | | | | | | | | | Signed-off-by: Robin Appelman <robin@icewind.nl>
* | | | Merge pull request #4659 from nextcloud/fix/ignore-empty-email-contacts-menuLukas Reschke2017-05-021-0/+24
|\ \ \ \ | |_|/ / |/| | | Do not show an email action for contacts with emtpy email addresses
| * | | Do not show an email action for contacts with emtpy email addressesChristoph Wurst2017-05-021-0/+24
| | |/ | |/| | | | | | | Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
* / | Fix testRoeland Jago Douma2017-05-021-20/+10
|/ / | | | | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* | Fix and update testsRoeland Jago Douma2017-05-021-65/+116
| | | | | | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* | Add missing spaceLukas Reschke2017-05-011-1/+1
| | | | | | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* | Mark IP as whitelisted if brute force protection is disabledLukas Reschke2017-05-011-8/+51
|/ | | | | | | | Currently, when disabling the brute force protection no new brute force attempts are logged. However, the ones logged within the last 24 hours will still be used for throttling. This is quite an unexpected behaviour and caused some support issues. With this change when the brute force protection is disabled also the existing attempts within the last 24 hours will be disregarded. Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* Rename “Server settings” to “Basic settings”Marius Blüm2017-04-291-2/+2
| | | | | | * fixes #4587 Signed-off-by: Marius Blüm <marius@lineone.io>
* consolidate setEnabled methodArthur Schiwon2017-04-291-12/+16
| | | | | | and fix a unit test Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
* UserManager can now count disabled usersArthur Schiwon2017-04-291-0/+25
| | | | | | Users page takes advantage of that Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
* fix unit testsMorris Jobke2017-04-291-16/+6
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* use proper return codes and handle failure casesMorris Jobke2017-04-291-4/+8
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Improve wording of error messagesMorris Jobke2017-04-291-6/+6
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* fix unit testsMorris Jobke2017-04-291-24/+13
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* add unit tests for enable methodMorris Jobke2017-04-291-1/+221
|
* add unit tests for disable methodMorris Jobke2017-04-291-1/+219
|
* adjust tests to have at least one disabled userMorris Jobke2017-04-291-2/+13
|
* Fix unit testsRoeland Jago Douma2017-04-291-1/+59
|
* Fix unit testsMorris Jobke2017-04-291-4/+4
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* fix unit testBjoern Schiessle2017-04-281-21/+24
| | | | Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
* fix email verification statusBjoern Schiessle2017-04-281-1/+1
| | | | Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
* updated unit testsBjoern Schiessle2017-04-281-6/+50
| | | | Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
* check verification proof and update account tableBjoern Schiessle2017-04-281-2/+104
| | | | Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
* Merge pull request #4522 from nextcloud/downstream-27596Morris Jobke2017-04-271-5/+11
|\ | | | | Allow to create a user for a specific backend
| * Use the new method in the old one to remove duplicate codeJoas Schilling2017-04-271-5/+11
| | | | | | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* | Merge pull request #4501 from nextcloud/downstream-27144Morris Jobke2017-04-261-9/+13
|\ \ | | | | | | Add duration of last job execution to the table
| * | Add duration of last job execution to the tableNoveen Sachdeva2017-04-251-9/+13
| | |
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-28 12:00:25 +0000