[E2E] generate unique names for PVC/PV and pod Names
Open
component/testing
keepalive
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 617
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 43
Description
With the current E2E it's difficult to identify the problem based on the PVC name or the pod name as we reuse the same name in multiple tests. It's good to generate a unique name each time which helps in debugging.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the repository's E2E tests that create PVCs, PVs, and pods, then identify where their names are assigned. Ensure each generated name is unique across test runs and confirm the resulting names make individual resources easier to identify during debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100