summaryrefslogtreecommitdiff
path: root/features/support/capybara.rb
Commit message (Collapse)AuthorAgeFilesLines
* Disable /dev/shm in CIsh-disable-dev-shmStan Hu2017-12-221-0/+3
| | | | | | | | | | | According to the Chrome source code (https://chromium.googlesource.com/chromium/src/base/+/master/base_switches.cc#120): The /dev/shm partition is too small in certain VM environments, causing Chrome to fail or crash (see http://crbug.com/715363). Use this flag to work-around this issue (a temporary directory will always be used to create anonymous shared memory files). Addresses gitlab-org/gitlab-ee#4252 but doesn't appear to cure it completely.
* add logging back to capybara config and clean up selenium option instantiationclean-capybara-configMike Greiling2017-11-291-8/+28
|
* enable CHROME_HEADLESS environment variable for Spinach tests similar to RSpecMike Greiling2017-11-011-1/+4
|
* Bump selenium-webdriver to 3.5.0 to make Capybara work properlyStan Hu2017-08-121-1/+1
|
* Expand Spinach window size and remove unsupported trigger callsStan Hu2017-08-111-1/+1
|
* Make Capybara::Screenshot work with headless ChromeStan Hu2017-06-161-0/+4
|
* Replace PhantomJS with headless Chrome for Rspec testsStan Hu2017-06-161-13/+9
| | | | Closes #30876
* Let PhantomJS load local imagesrc/load-images-in-phantomjsRémy Coutable2017-06-121-1/+3
| | | | | | | | | | | | | This change fix a memory leak due to a Webkit bug: https://github.com/ariya/phantomjs/issues/12903 Also: - Whitelist only localhost and 127.0.0.1 in Capybara + JS specs - Blacklist all requests to media such as images, videos, PDFs, CSVs etc. - Log all the requests made. Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix a Knapsack issue that would load support/capybara.rb before support/env.rbrc/fix-spinach-plus-knapsack-properlyRémy Coutable2017-04-041-3/+0
| | | | | | | | Once https://github.com/ArturT/knapsack/issues/57 is solved and released in a new gem version, we can remove the KNAPSACK_TEST_DIR in .gitlab-ci.yml. Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix Spinach and Capybara dependenciesStan Hu2017-04-011-1/+3
| | | | Closes #30347
* Properly eagerly-load the Capybara server for JS feature specs onlyRémy Coutable2017-03-311-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Eager-load the Capybara server to prevent timeoutsRémy Coutable2017-03-311-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Increase Capybara's timeoutRémy Coutable2017-03-311-1/+1
| | | | | | | | Also disabled assets warming for Capybara/RSpec and remove a check to skip assets warming when ./tmp/cache/assets/test exists because assets are now served by webpack-dev-server. Signed-off-by: Rémy Coutable <remy@rymai.me>
* Merge branch 'rs-capybara-screenshot-artifacts' into 'master' Kamil Trzciński2017-03-141-6/+3
|\ | | | | | | | | | | | | Store capybara screenshots as build artifacts Closes #13971 See merge request !7985
| * Don't disable capybara-screenshot in CI environmentrs-capybara-screenshot-artifactsRobert Speicher2016-12-081-6/+3
| |
* | Decrease Capybara timeout for CI environmentrs-lower-capybara-timeoutRobert Speicher2017-03-081-1/+1
|/
* Pass `--load-images=no` to PhantomJS via Capybara/Poltergeistrs-phantomjs-disable-imagesRobert Speicher2016-11-281-1/+9
| | | | | | We were unintentionally hitting `gravatar.com` whenever a test that used Poltergeist was run. This was certainly wasting their resources and slowing down our tests even further, for no reason.
* Disable warming of the asset cache in Spinach tests under CIStan Hu2016-10-211-1/+1
| | | | | | | | | | | | I suspect some combination of Knapsack tests cause no regular Rack tests to be loaded (i.e. all JavaScript tests), which leads to the error: ArgumentError: rack-test requires a rack application, but none was given In CI, we precompile all the assets so there is no need to warm the asset cache in any case. Closes #23613
* Fix Capybara 2.6.2 deprecation warningsStan Hu2016-03-151-1/+1
|
* Set window_size to 1366*768Alfredo Sumaran2016-02-231-1/+1
|
* Prevent transient Capybara timeouts during feature testsrs-transient-capybara-timeoutRobert Speicher2016-01-281-4/+4
| | | | | | | | | | | The problem occurred because asset compilation takes a long time, so when the asset cache didn't exist and the first test ran, it would often (randomly) time out during the generation before the actual test even had a chance to run. Now we check if the cache exists before the suite runs, and if not, we manually fire a request to the root URL in order to generate it. This should allow subsequent tests to use the cached assets.
* Add spinach test for note pollingGrzegorz Bizon2015-12-151-1/+1
| | | | | This also increases capybara timeout to 15 seconds (note polling interval). Capybara will look for new note for this period of time.
* Don't use capybara-screenshot in CI environmentsrs-capybara-screenshotRobert Speicher2015-04-251-3/+5
|
* Enable js_errors for Capybara in Spinach and RSpecRobert Speicher2015-04-251-1/+1
|
* Reduce timeout for non-CI featuresRobert Speicher2015-04-251-2/+5
|
* Move Spinach setup for db_cleaner and capybara to their own filesRobert Speicher2015-04-251-0/+19
Also adds capybara-screenshot, which will automatically save the page as html and an image whenever a feature fails. Handy for debugging.
View Lorry Controller Status