bbe0fa91d0
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. |
||
|---|---|---|
| .. | ||
| api | ||
| gitlab_stubs | ||
| matchers | ||
| api_helpers.rb | ||
| capybara.rb | ||
| capybara_helpers.rb | ||
| db_cleaner.rb | ||
| factory_girl.rb | ||
| filter_spec_helper.rb | ||
| fixture_helpers.rb | ||
| jira_service_helper.rb | ||
| login_helpers.rb | ||
| markdown_feature.rb | ||
| mentionable_shared_examples.rb | ||
| relative_url.rb | ||
| repo_helpers.rb | ||
| select2_helper.rb | ||
| services_shared_context.rb | ||
| setup_builds_storage.rb | ||
| stub_configuration.rb | ||
| stub_gitlab_calls.rb | ||
| stub_gitlab_data.rb | ||
| taskable_shared_examples.rb | ||
| test_env.rb | ||
| wait_for_ajax.rb | ||
| webmock.rb | ||