summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #5009 from nextcloud/update-acceptance-tests-for-issue-4921Roeland Jago Douma2017-05-221-1/+10
|\ | | | | Update acceptance tests for issue #4921
| * Update acceptance tests for issue #4921Daniel Calviño Sánchez2017-05-211-1/+10
| | | | | | | | | | | | | | | | | | Acceptance tests opened the details view by clicking on the middle of the file row, but due to the changes made in issue #4921 that now opens the file instead; this commit updates the acceptance tests to open the details view through the "Details" item in the file actions menu. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* | Fix testsLukas Reschke2017-05-202-6/+15
|/ | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* Merge pull request #4894 from nextcloud/generic-security-activitiesLukas Reschke2017-05-194-4/+292
|\ | | | | Change 2FA activities to more generic security activities
| * Fix testsRoeland Jago Douma2017-05-181-4/+4
| | | | | | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
| * Move activities test codeChristoph Wurst2017-05-183-0/+288
| | | | | | | | Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
* | Merge pull request #4792 from nextcloud/fix-storage-wrappers-on-scannerLukas Reschke2017-05-191-0/+47
|\ \ | | | | | | Make sure we use the passed-in storage when there is one
| * | use unmasked permissions during scanningRobin Appelman2017-05-181-0/+47
| | | | | | | | | | | | Signed-off-by: Robin Appelman <robin@icewind.nl>
* | | Adjust token nameLukas Reschke2017-05-181-1/+1
| | | | | | | | | | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* | | Add tests for OAuth2 appLukas Reschke2017-05-181-0/+1
| | | | | | | | | | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* | | Add test for DefaultTokenMapperLukas Reschke2017-05-181-0/+11
| | | | | | | | | | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* | | Rename table back to lowercaseLukas Reschke2017-05-181-6/+10
| | | | | | | | | | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* | | Add tests for ClientFlowLoginControllerLukas Reschke2017-05-181-19/+181
| | | | | | | | | | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* | | delete auth token when client gets deletedBjoern Schiessle2017-05-181-6/+6
| |/ |/| | | | | Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
* | Merge pull request #4666 from nextcloud/enable-redis-clusterMorris Jobke2017-05-161-0/+20
|\ \ | | | | | | Add redis cluster tests to our CI jobs
| * | Add redis cluster tests to our CI jobsMorris Jobke2017-05-111-0/+20
| | | | | | | | | | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* | | Merge pull request #4816 from nextcloud/Ardinis-quota-files_externalMorris Jobke2017-05-121-3/+3
|\ \ \ | | | | | | | | Correctly calculate used space for quota with external storage
| * | | fix quota tests for external storageMorris Jobke2017-05-121-3/+3
| |/ / | | | | | | | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* | | Merge pull request #4809 from nextcloud/downstream-27676Lukas Reschke2017-05-121-15/+7
|\ \ \ | | | | | | | | Disable reset password link
| * | | Disable the API endpoints as wellJoas Schilling2017-05-111-15/+7
| |/ / | | | | | | | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* | | Merge pull request #4825 from nextcloud/add-timeout-appstoreLukas Reschke2017-05-121-1/+5
|\ \ \ | | | | | | | | Add timeout for requests to appstore
| * | | Fix failed assertionsJoas Schilling2017-05-121-1/+5
| |/ / | | | | | | | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* / / Fix unit testsJoas Schilling2017-05-123-2/+12
|/ / | | | | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* | 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>