Add operator lifecycle e2e coverage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 9h 55m
- Merged PRs (30d)
- 25
Description
Add end-to-end scenarios that exercise project CRs, not only deployment health and metrics. At minimum, cover a supported ClusterPool, ClusterInstance, ClusterLease, or CRCBundle lifecycle and validate statuses, backing resources, binding, and cleanup where practical.\n\nCurrent suite: test/e2e/e2e_test.go
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading and running the current end-to-end suite in test/e2e/e2e_test.go to understand its existing deployment health and metrics coverage. Add scenarios for at least one supported project CR lifecycle, validating statuses, backing resources, binding, and cleanup where practical. Done means the suite exercises the selected lifecycle end to end.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100