-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
repair allocation system tests #117
Labels
Comments
Closed
Closed
stewartie4
added
the
blocked by development
Blocked by development issues not finished
label
Dec 16, 2022
boddumanohar
assigned aniketsingh03 and boddumanohar and unassigned boddumanohar and aniketsingh03
Feb 28, 2023
guruhubb
changed the title
repair allocation system tests
repair allocation system tests + use repair for add/replace blobber
Mar 23, 2023
boddumanohar
changed the title
repair allocation system tests + use repair for add/replace blobber
repair allocation system tests
Apr 14, 2023
Merged
there is no reason to make repair in cli, it will be done automatically in gosdk during normal functionality. we will test it in conductor tests other than #731 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Investigate and Implement system acceptance tests that test allocation repair functionality
Example test cases are below but this is not a complete list.
Also create your own, thinking about security, param validation, error messaging, performance etc.
attempt file repair on single file that needs repaired
attempt file repair on multiple files that needs repaired
attempt file repair on file that does need repaired with a file that does not need repaired
attempt file repair on file that does not exist
attempt file repair using local path that does not exist
don't supply repair path
don't supply root path
Repair by delete
Repair by upload
a system test where we replace all blobbers with new ones with no data loss
Following the test style guide and the style of the existing tests
The text was updated successfully, but these errors were encountered: