mayadata-io / mayadata-io/oep-e2e
review(dmaas): add s3 full & different storage class scenarios
Open
Nobody has claimed this yet.
dmaas
negative
testplan
- Dominant language
- Python
- Stars
- 6
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Looks good to me. For DMaaS it might be good to call out the full list of objects that will be backed up, verify that they're all present in the restored application. Also, if we're looking for negative test cases, we can add:
- Back up to a minIO that's full (and expected to fail)
- Restore to the same namespace in a different cluster that has storage classes that are different (e.g. ext4 instead of XFS)
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 locating the existing DMaaS S3 backup and restore scenarios and their object assertions. Add coverage for a full minIO backup and restoring into the same namespace on a different cluster with different storage classes, then verify the expected failures and restored objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100