Page Comparison

...

1. Attempt to delete a existing file on a pillar, supplying a correct checksum.
   
   1. The file should have been removed from the collection. Use the getFileIDs and getChecksums operation to verify the deletion.
2. Attempt to delete a the file again.
   
   1. The operation should still return succesfully because of the deleteFile idempotent behavior.
3. Attempt to delete a file in a different collection.
   1. The file should have been removed from the collection. Use the getFileIDs and getChecksums operation to verify the deletion.

Delete with returned checksum

...

1. Attempt to delete a existing file on a pillar, supplying a incorrect checksum.
   1. 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 and getChecksums operation to verify the deletion.

Missing file delete

1. Attempt to delete a file that does not exist in the collection.
   1. The pillar should inform the user that no file was delete, as the given file ID didn't exist.
   2. (Idempotent) The operation should be considered successfull, e.g. the final event should be 'Complete'.