e2e tests: document test cases - Githubissues

RamenDR / ramen

Apache License 2.0

73 stars 56 forks source link

e2e tests: document test cases #134

Open tjanssen3 opened 3 years ago

tjanssen3 commented 3 years ago

Can create an issue or empty doc

(from HackMD list)

ShyamsundarR commented 1 year ago

Here is an initial structure/list of e2e tests that we can start automating:

Questions:

Should we start at a given drenv and test from deploy->configure->functionality, or start at a configured point?

Test areas:

Test creation of DRCluster with valid/invalid parameters
Test creation of DRPolicy with valid/invalid parameters
Test creation of Fencing resources with valid/invalid parameters
Test DRPC/VRG functionality with
- NOTE: Each line below is to represent a separate set of combinations
- VR|VolSync|VR+VolSync|Metro(FS+RBD)|Recipe
- Subscriptions|AppSets
- Placement|PlacementRule
- Pods|Deployments|STS|Operator
  - Scale up|down as applicable
- Single|Multi PVCs
- Resize|Creation of new PVC|Deletion of PVC
- Multiple apps
  - Failover as a group
  - Relocate as a group
- Hub restore cases
- Operations per type:
  - Deploy -> Relocate -> Failover -> Relocate -> Relocate -> Failover -> Failover
  - Disable -> Reenable -> Relocate -> Failover -> Relocate -> Relocate -> Failover -> Failover
  - Disable -> Delete
- Uninstall ramen workflow