Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
  • gitlab-ce
  • lib
  • gitlab
  • testing
  • request_blocker_middleware.rb
Find file BlameHistoryPermalink
  • Rémy Coutable's avatar
    Introduce a new middleware for the test environment that can block requests · 645a55f1
    Rémy Coutable authored Mar 10, 2017
    
    
    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: default avatarRémy Coutable <remy@rymai.me>
    645a55f1
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7