From c85a18e9bf296cef14e36cf52599b6749f022dd8 Mon Sep 17 00:00:00 2001 From: Go MAEDA Date: Thu, 19 Nov 2020 05:11:59 +0000 Subject: Adds CAPYBARA_SERVER_HOST, CAPYBARA_SERVER_PORT, SELENIUM_REMOTE_URL and CAPYBARA_APP_HOST to allow running system tests on a remote Selenium hub (on CI using Docker images) (#34269). Patch by Marius BALTEANU. git-svn-id: http://svn.redmine.org/redmine/trunk@20428 e93f8b46-1217-0410-a6f0-8f06a7374b81 --- doc/RUNNING_TESTS | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc') diff --git a/doc/RUNNING_TESTS b/doc/RUNNING_TESTS index 983b79107..5dec68c23 100644 --- a/doc/RUNNING_TESTS +++ b/doc/RUNNING_TESTS @@ -72,6 +72,14 @@ https://sites.google.com/a/chromium.org/chromedriver/ Capybara tests can be run with: `rails test:system` +The following environment variables can be used to configure your system tests setup: +`CAPYBARA_SERVER_HOST`: configure server to run on a custom IP which can be, for example, your remote Selenium IP or 0.0.0.0 to listen an all connections +`CAPYBARA_SERVER_PORT`: configure server port +`SELENIUM_REMOTE_URL`: remote Selenium URL +`CAPYBARA_APP_HOST`: by default, the tests expect to have the application running on your localhost. Using this variable, you can set a custom URL + +One use case of these variables is to run the system tests on a remote Selenium/ChromeDriver (eg: Docker). + Running RuboCop, a static code analyzer ======================================= -- cgit v1.2.3