Skip to content
Snippets Groups Projects
Select Git revision
  • move-gl-dropdown
  • improve-table-pagination-spec
  • move-markdown-preview
  • winh-fix-merge-request-spec
  • master default
  • index-namespaces-lower-name
  • winh-single-karma-test
  • 10-3-stable
  • 36782-replace-team-user-role-with-add_role-user-in-specs
  • winh-modal-internal-state
  • tz-ide-file-icons
  • 38869-milestone-select
  • update-autodevops-template
  • jivl-activate-repo-cookie-preferences
  • qa-add-deploy-key
  • docs-move-article-ldap
  • 40780-choose-file
  • 22643-manual-job-page
  • refactor-cluster-show-page-conservative
  • dm-sidekiq-versioning
  • v10.4.0.pre
  • v10.3.0
  • v10.3.0-rc5
  • v10.3.0-rc4
  • v10.3.0-rc3
  • v10.3.0-rc2
  • v10.2.5
  • v10.3.0-rc1
  • v10.0.7
  • v10.1.5
  • v10.2.4
  • v10.2.3
  • v10.2.2
  • v10.2.1
  • v10.3.0.pre
  • v10.2.0
  • v10.2.0-rc4
  • v10.2.0-rc3
  • v10.1.4
  • v10.2.0-rc2
40 results

test_env.rb

Forked from GitLab.org / GitLab FOSS
28997 commits behind the upstream repository.
  • Robert Speicher's avatar
    bbe0fa91
    Prevent transient Capybara timeouts during feature tests · bbe0fa91
    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.
    bbe0fa91
    History
    Prevent transient Capybara timeouts during feature tests
    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.
test_env.rb 5.38 KiB