etcd-io / etcd-io/etcd-operator
Unneeded e2e tear down steps
- Dominant language
- Go
- Stars
- 164
- Forks
- 72
- Avg merge
- 21h 20m
- Merged PRs (30d)
- 33
Description
testEnv.Finish has a number of steps which are not required and flood the terminal with extra information which make it harder to view test results.
Steps such as removing the namespaces, CRDS etc are not required if the kind cluster is being removed. These could be reasonable when testing against a persistent cluster instead of an ephemeral one such as Kind.
I'm happy to work on this issue
Contributor guide
Research direction
Start by locating testEnv.Finish and tracing its e2e teardown steps for the Kind cluster, including namespace and CRD removal. Confirm which cleanup is redundant for an ephemeral cluster, then verify that test results are less noisy while cleanup for persistent clusters remains appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100