2018-06-05 staging failover test plan
Failover Test Plan
README
If you are volunteering, please make yourself available to join the GCP Migration Rehearsal call. Ping @andrewn or @meks for an invite.
- Zoom link: https://gitlab.zoom.us/j/859814316
- Slack channel: #gcp_migration
High-level Overview
This test plan requires some manual testing as well as some automated testing using [GitLab QA].
The automated and manual QA processes can be conducted in parallel with one another.
The plan will also involve testing during two distinct phases of the failover plan:
-
During the Blackout (inside the maintenance window period):
- All the tests conducted during this period are related to features critical to the operation of GitLab.com.
- The maintenance window cannot be closed until these tests pass.
-
After the Blackout (after the maintenance window period):
- These tests are non-critical, but, in order to keep the maintenance window as short as possible, should be conducted after the new failover GitLab instance is public.
Automated QA
During the Blackout
@meks / @remy to run [GitLab QA] against failed-over environment.
-
Automated QA complete with 100% pass env GITLAB_USERNAME=gitlab-qa GITLAB_PASSWORD=... gitlab-qa Test::Instance::Any EE latest https://staging.gitlab.com
Finished in 32 minutes 35 seconds (files took 12.6 seconds to load) 23 examples, 12 failures
## Manual QA
**Manual test plan:** https://docs.google.com/spreadsheets/d/1Ti5jo3Xq3SoRVjaLOpsomxLPH12L0FyK3wLresKlgE0/edit#gid=0
[GitLab QA]: https://gitlab.com/gitlab-org/gitlab-qa
/cc @remy
Edited by Rémy Coutable