Create abstract ProviderFiller interface for e2e tests
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
Currently, the e2e tests utilize a provider-typed Filler (e.g. VSphereFiller) which is used to modify and customize the e2e test framework. A similar provider-specific approach has been taken with CloudStack in https://github.com/aws/eks-anywhere/pull/1676. We should instead implement an interface that accepts both CloudStack and VSphere test fillers
**Why is this needed**:
In order to avoid duplicating so much e2e test code
Contributor guide
Research direction
Start by locating the e2e test framework's provider-typed Filler and the VSphereFiller implementation, then compare them with the CloudStack approach in pull request 1676. Done means both CloudStack and VSphere test fillers can use one abstract interface without duplicating the e2e test code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100