- 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>
-
- 03 Apr, 2017 1 commit
-
-
Rémy Coutable authored
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>
-
- 02 Apr, 2017 1 commit
-
-
Stan Hu authored
Closes #30347
-
- 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.
-
- 21 Oct, 2016 1 commit
-
-
Stan Hu authored
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
-
- 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.
-
- 15 Dec, 2015 1 commit
-
-
Grzegorz Bizon authored
This also increases capybara timeout to 15 seconds (note polling interval). Capybara will look for new note for this period of time.
-
- 26 Apr, 2015 4 commits
-
-
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.
-