- 11 Jan, 2018 1 commit
-
-
🙈 jacopo beschi 🙉 authored
-
- 02 Nov, 2017 1 commit
-
-
Mike Greiling authored
-
- 16 Jun, 2017 3 commits
-
-
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>
-
Stan Hu authored
-
Stan Hu authored
-
- 15 Jun, 2017 1 commit
-
-
Stan Hu authored
From logs in #33756, we that it's possible for an Ajax call to be made before the middleware receives it. To prevent stray Ajax calls from breaking other specs, we need to wait for all scheduled calls to finish. Closes #33756
-
- 22 May, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 12 May, 2017 1 commit
-
-
Douwe Maan authored
-
- 09 May, 2017 1 commit
-
-
Fatih Acet authored
-
- 26 Apr, 2017 1 commit
-
-
Rémy Coutable authored
Hopefully, this can solve transient failures such as https://gitlab.com/gitlab-org/gitlab-ce/issues/29836. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 22 Mar, 2017 2 commits
-
-
Rémy Coutable authored
This turned out to prevent the browser from clearing the local storage. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
The idea is that after each feature spec example, we block all incoming requests at the Rack level, go to the 'about:blank' page, and wait until the current requests reach 0. This should solve the problem where a request would end after database cleaner performed the database truncation. The problem was that a GET request can still lead to records creation (e.g. namespaces or routes). Signed-off-by: Rémy Coutable <remy@rymai.me>
-