nextcloud/tests/acceptance/config/behat.yml

default:
  autoload:
    '': %paths.base%/../features/bootstrap
  suites:
    default:
      paths:
        - %paths.base%/../features
      contexts:
        - ActorContext
        - NextcloudTestServerContext

        - AppNavigationContext
        - CommentsAppContext
        - FeatureContext
        - FileListContext
        - FilesAppContext
        - FilesSharingAppContext
        - LoginPageContext
        - NotificationContext
        - SettingsContext
        - SettingsMenuContext
        - ThemingAppContext
        - UsersSettingsContext
  extensions:
    Behat\MinkExtension:
      sessions:
        default:
          selenium2: ~
        John:
          selenium2: ~
        Jane:
          selenium2: ~
Add basic files for the automated acceptance test system The acceptance tests verify that a Nextcloud server works as expected from the point of view of an end-user. They are specified as user stories using Behat paired with Mink, which provides web browser automation. Mink supports several browser emulators, but the system is set up to use Selenium, as it is FOSS and the one that better reflects the use of a web browser by an end-user (as, in fact, it controls real web browsers). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 17:11:20 +03:00			`default:`
			`autoload:`
			`'': %paths.base%/../features/bootstrap`
			`suites:`
			`default:`
			`paths:`
			`- %paths.base%/../features`
			`contexts:`
Add actors for test scenarios An actor plays the role of an end-user in the test scenario. As such, each actor has its own web browser session used to perform the actions specified by the steps of the scenario. Only one actor is active at a time in a test scenario, and the current actor can be set through the "I act as XXX" step; from then on, all the steps are performed by that actor, until a different actor is set by calling "I act as XXX" again. If no actor was explicitly set in a scenario then the default actor, unsurprisingly named "default", is the one used. The ActorContext class is added to provide automatic support for all that. To use the ActorContext, besides adding it to the context list in "behat.yml", a Mink session for each actor used in the features must be specified in "behat.yml". Once done other Contexts just need to implement the ActorAwareInterface (which can be done simply by using the ActorAware trait) to have access to the current Actor object of the test scenario; as the Actor object provides its own session other Contexts do not need to extend from RawMinkContext. The ActorContext is itself a RawMinkContext, so it automatically receives the base URL of the Nextcloud test server run by NextcloudTestServerContext and propagates that base URL to all the actors. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 17:18:05 +03:00			`- ActorContext`
Add helper context to isolate the test server with Docker containers Scenarios in acceptance tests must be independent one of each other. That is, the execution of one scenario can not affect the execution of another scenario, nor it can depend on the result of the execution of a different scenario. Each scenario must be isolated and self-contained. As the acceptance tests are run against a Nextcloud server the server must be in a known and predefined initial state each time a scenario begins. The NextcloudTestServerContext is introduced to automatically set up the Nextcloud test server for each scenario. This can be achieved using Docker containers. Before an scenario begins a new Docker container with a Nextcloud server is run; the scenario is then run against the server provided by the container. When the scenario ends the container is destroyed. As long as the Nextcloud server uses local data storage each scenario is thus isolated from the rest. The NextcloudTestServerContext also notifies its sibling RawMinkContexts about the base URL of the Nextcloud test server being used in each scenario. Although it uses the Behat context system, NextcloudTestServerContext is not really part of the acceptance tests, but a provider of core features needed by them; it can be seen as part of a Nextcloud acceptance test library. Therefore, those classes are stored in the "core" directory instead of the "bootstrap" directory. Besides its own (quite limited) autoload configuration, Behat also uses the Composer autoloader, so the "core" directory has to be added there for its classes to be found by Behat. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 17:11:34 +03:00			`- NextcloudTestServerContext`

Extract app navigation elements to its own context The app navigation is not exclusive to the Files app but a generic component used by other apps too, so its locators and steps should be in its own context. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-07-08 16:36:01 +03:00			`- AppNavigationContext`
add acceptance tests Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de> 2017-10-29 00:57:35 +03:00			`- CommentsAppContext`
Add basic files for the automated acceptance test system The acceptance tests verify that a Nextcloud server works as expected from the point of view of an end-user. They are specified as user stories using Behat paired with Mink, which provides web browser automation. Mink supports several browser emulators, but the system is set up to use Selenium, as it is FOSS and the one that better reflects the use of a web browser by an end-user (as, in fact, it controls real web browsers). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 17:11:20 +03:00			`- FeatureContext`
Extract file list locators and steps to its own class Besides the extraction some minor adjustments (sorting locators for file action menu entries to reflect the order of the menu entries in the UI, moving parametrized locators like "createMenuItemFor" above the locators that use them and placing "descendantOf" calls always in a new line) were made too. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2018-02-19 01:52:44 +03:00			`- FileListContext`
Add acceptance tests related to login Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 18:20:19 +03:00			`- FilesAppContext`
Add acceptance tests for sharing password protected links Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-22 19:20:32 +03:00			`- FilesSharingAppContext`
Add acceptance tests related to login Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 18:20:19 +03:00			`- LoginPageContext`
			`- NotificationContext`
Add acceptance tests for unselecting items in dropdown for tags Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-07-08 16:46:16 +03:00			`- SettingsContext`
Add acceptance tests related to login Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 18:20:19 +03:00			`- SettingsMenuContext`
Add acceptance tests for setting the color in the Theming app Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-08-04 14:20:22 +03:00			`- ThemingAppContext`
Add acceptance tests related to login Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 18:20:19 +03:00			`- UsersSettingsContext`
Add basic files for the automated acceptance test system The acceptance tests verify that a Nextcloud server works as expected from the point of view of an end-user. They are specified as user stories using Behat paired with Mink, which provides web browser automation. Mink supports several browser emulators, but the system is set up to use Selenium, as it is FOSS and the one that better reflects the use of a web browser by an end-user (as, in fact, it controls real web browsers). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 17:11:20 +03:00			`extensions:`
			`Behat\MinkExtension:`
			`sessions:`
			`default:`
			`selenium2: ~`
Add acceptance tests related to login Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> 2017-04-04 18:20:19 +03:00			`John:`
			`selenium2: ~`
			`Jane:`
			`selenium2: ~`