-
Notifications
You must be signed in to change notification settings - Fork 18
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
Create a test plan for partial implementation of Object Lock #405
Comments
Object Lock Test PlanObjectiveTo validate the functionality, reliability, and performance of the object Lock feature to ensure it meets the requirements for object immutability and retention policies and only tests items within the scope of our implementation. Scope
Test Cases:Enable Object Lock:
Retention Periods:
New Actions:
Modifications to existing endpoints:
Legal Hold:
Governance Mode
Performance TestingData Access Performance:
Error Handling and Edge CasesInvalid Operations:
ConclusionThis test plan outlines a comprehensive approach to validate Object Lock feature's functionality, security, and performance. By executing this plan, we can ensure that the Object Lock feature works as intended, providing the necessary immutability and protection for stored objects. |
@neo-cypher A few things that should be reflected in the test plan:
|
@kaloyan-raev, I appreciate you taking the time to review this test plan. I had the scope incorrect so it skewed the requirements. Thanks for the corner cases, those are super helpful; as well as pointing out that when object lock is enabled that object versioning too is enabled and cannot be disabled or suspended. I'll get this feedback into the plan and update the scope to match our MVPs. |
A few things that should be reflected in the test plan:
|
Goal
This issue is to make meaningful progress on Object Lock implementation within core and edge services. Specifically, to support immutable backups in backup software products like Veeam.
What needs to be done? • Acceptance Criteria
We only need to implement a small subset of Object Lock (for example, Legal Hold is out of scope at this moment) first. What needs to be implemented is defined in Object Lock milestone MVP section. To recap, it's:
What needs to be done is a test plan to
Use a known template for test plans, if there is one.
Depends on…
This issue does not depend on anything and can be worked on immediately.
Links
The text was updated successfully, but these errors were encountered: