Excerpt |
---|
Describes the tests needed to validate the Delete functionality. |
...
Basic delete
- Attempt to delete a existing file on a pillar, supplying a correct checksum.
- The file should have been removed from the collection. Use the
getFileIDs
andgetChecksums
operation to verify the deletion.
- The file should have been removed from the collection. Use the
Delete with returned checksum
- Attempt to delete a existing file on a pillar, requesting the return of a pillar calculated,salted checksum.
- The file
...
- should have been removed from the collection and a checksum should have been returned.
- Delete the
...
- file on a different pillar, requesting the return of a pillar calculated,salted checksum.
- Verify that the returned checksums are the same.
Bad checksum delete
- Attempt to delete a existing file
...
- on a pillar, supplying a incorrect checksum.
- The file should have been not have been removed from the collection and the pillar should inform the user that the cause was the incorrect checksum. Use the
getFileIDs
andgetChecksums
operation to verify the deletion.
- The file should have been not have been removed from the collection and the pillar should inform the user that the cause was the incorrect checksum. Use the
Missing file delete
- Attempt to delete a file that does not exist in the collection.
- The pillar should inform the user that no file was delete, as the given file ID didn't exist.
Child pages (Children Display) | ||||
---|---|---|---|---|
|