Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
team-tasks
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 302
    • Issues 302
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • quality
  • team-tasks
  • Issues
  • #385

Closed
Open
Created Feb 13, 2020 by Jennifer Louie@jennielouie🔴Owner

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
None
Milestone
None
Assign milestone
Time tracking