Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • T team-tasks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 519
    • Issues 519
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • Quality DepartmentQuality Department
  • Quality Engineering
  • team-tasks
  • Issues
  • #385
Closed
Open
Issue created Feb 13, 2020 by Jennifer Louie@jennielouie🔴

Run Geo end-to-end tests on staging

Once Geo in enabled on staging, we should regularly run Geo end-to-end tests.

Some considerations:

  • This may involve changes to files in multiple projects: gitlab-qa, pipeline-common, staging
  • Geo tests require an EE license and secondary node URL. The current Test::Instance::Staging scenario does not support either of those (Test:: Instance::Geo scenario does support those inputs)
  • When and how often should Geo end-to-end tests run on staging?
  • Is there any additional documentation or demos required to help SETs/Engineers investigate Geo test failures on staging (or in general)?
Assignee
Assign to
Time tracking