An error occurred fetching the project authors.
- 23 Feb, 2018 1 commit
-
-
Mike Greiling authored
-
- 22 Dec, 2017 1 commit
-
-
Stan Hu authored
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.
-
- 29 Nov, 2017 1 commit
-
-
Mike Greiling authored
-
- 01 Nov, 2017 3 commits
-
-
Mike Greiling authored
-
Mike Greiling authored
-
Mike Greiling authored
-
- 21 Oct, 2017 1 commit
-
-
Mike Greiling authored
-
- 20 Oct, 2017 1 commit
-
-
Mike Greiling authored
-
- 13 Aug, 2017 1 commit
-
-
Stan Hu authored
-
- 12 Aug, 2017 1 commit
-
-
Stan Hu authored
-
- 28 Jul, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 22 Jun, 2017 1 commit
-
-
Douwe Maan authored
Don't reset the session when the example failed, because we need capybara-screenshot to have access to it
-
- 17 Jun, 2017 2 commits
- 16 Jun, 2017 1 commit
-
-
Rémy Coutable authored
capybara/rspec already calls Capybara.reset_sessions! in an `after` hook, but `block_and_wait_for_requests_complete` is called before it so by calling it explicitely here, we prevent any new requests from being fired. See https://github.com/teamcapybara/capybara/blob/ffb41cfad620de1961bb49b1562a9fa9b28c0903/lib/capybara/rspec.rb#L20-L25Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 12 Jun, 2017 1 commit
-
-
Rémy Coutable authored
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>
-
- 31 Mar, 2017 3 commits
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
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>
-
- 08 Mar, 2017 1 commit
-
-
Robert Speicher authored
-
- 08 Dec, 2016 1 commit
-
-
Robert Speicher authored
-
- 28 Nov, 2016 1 commit
-
-
Robert Speicher authored
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.
-
- 15 Mar, 2016 1 commit
-
-
Stan Hu authored
-
- 23 Feb, 2016 1 commit
-
-
Alfredo Sumaran authored
-
- 29 Jan, 2016 1 commit
-
-
Robert Speicher authored
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.
-
- 22 Jun, 2015 1 commit
-
-
Robert Speicher authored
In case we end up wanting to use it in Spinach as well.
-
- 15 Jun, 2015 1 commit
-
-
Robert Speicher authored
-
- 26 Apr, 2015 5 commits
-
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
Also adds capybara-screenshot, which will automatically save the page as html and an image whenever a feature fails. Handy for debugging.
-