Describes the tests needed to validate the Replace functionality.
Basic replace
- Attempt to replace a file. The file should exist in the collection, providing the correct checksum for the existing file.
- The new file should now be the one in the collection. Use the getChecksum client to verify this.
Bad old file checksum
- Attempt to replace a file, providing the wrong checksum for the old file.
- The file shouldn't be replaced, and the user should be informed that the operation failed due to the invalid checksum for the old file.
Missing file replace
- Attempt to replace a file that does not exist in the collection.
- The user should be informed that the operation failed because the file did't exist.
Replace with returned checksums
- Replace a file with including the a request of a salted checksum calculated on the pillars, which should be returned.
- Check that the file is replaced correctly, and that the returned checksums are correct and consistent across the responses returned by the pillars).
Open issues